You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 5, 2023. It is now read-only.
We've been encountering an issue with the logger not posting to CloudWatch after having upgraded our ECS host instances to Ubuntu 18.04. After some investigation, we realised that journald inside the Docker image could not read the journal from our host instance:
Also, we've had a slight issue with the Readme that says that we should be using /run/log/journald as a mounting point but, in Ubuntu 18.04, the default logging folder is /var/log/journald, so we had to change the source mount point for the bind mount.
A solution could be to update systemd running inside the instance from systemd sources: systemd/systemd#3875 - that operation could be done in your Dockerfile.
Hi Segment team @achille-roussel @jnjackins ,
We've been encountering an issue with the logger not posting to CloudWatch after having upgraded our ECS host instances to Ubuntu 18.04. After some investigation, we realised that
journaldinside the Docker image could not read the journal from our host instance:Also, we've had a slight issue with the Readme that says that we should be using
/run/log/journaldas a mounting point but, in Ubuntu 18.04, the default logging folder is/var/log/journald, so we had to change the source mount point for the bind mount.A solution could be to update
systemdrunning inside the instance from systemd sources: systemd/systemd#3875 - that operation could be done in your Dockerfile.Cheers!