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 has been archived by the owner on Feb 24, 2023. It is now read-only.
I'm running an Erlang service in a container through systemd-docker. This service's foreground process is an Erlang console, which requires a TTY to be able to run.
If I run a container with the -t flag which makes Docker allocate a pseudo-TTY, the output of the container is seemingly lost. Is there a way to work around this?
The text was updated successfully, but these errors were encountered:
I've found a workaround for the Erlang specific problem that required a TTY, but I'm going to leave this open to figure out if there's a way to catch the output of a pseudo-TTY.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey,
I'm running an Erlang service in a container through
systemd-docker
. This service's foreground process is an Erlang console, which requires a TTY to be able to run.If I run a container with the
-t
flag which makes Docker allocate a pseudo-TTY, the output of the container is seemingly lost. Is there a way to work around this?The text was updated successfully, but these errors were encountered: