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 Dec 24, 2019. It is now read-only.
It may seem strange, but executing the scava docker containers in the shell (in a screen more precisely) now scrambles up my terminal -- see screenshot. It happens only and exclusively in the terminal where I started the scava app (using docker-compose).
I've already seen such weird screens when some binary data (with a unlucky character sequence in it) has been output to the terminal. Could it be that some container does that?
Note that the containers are still working fine, so not a big worry. But slightly frustrating. ;-)
The text was updated successfully, but these errors were encountered:
I have previously used screen to keep the containers running without keeping the ssh session open and I have never seen something similar. I'll try to test it on Monday if the DNS in our server is fixed.
I have previously used screen to keep the containers running without keeping the ssh session open and I have never seen something similar. I'll try to test it on Monday if the DNS in our server is fixed.
I'm using screen too and have experienced something similar on my side, rather recently like two weeks ago. Maybe one or two times. The only reason for this that raise into my mind is one of the container output produce a control character that scrambles the terminal.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It may seem strange, but executing the scava docker containers in the shell (in a screen more precisely) now scrambles up my terminal -- see screenshot. It happens only and exclusively in the terminal where I started the scava app (using docker-compose).
I've already seen such weird screens when some binary data (with a unlucky character sequence in it) has been output to the terminal. Could it be that some container does that?
Note that the containers are still working fine, so not a big worry. But slightly frustrating. ;-)
The text was updated successfully, but these errors were encountered: