Open davidediruscio opened 4 years ago
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.
It's fairly new, happened for the first time this week only. Never happened before when running scava, so it must be a quite new feature/commit.
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.
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. ;-)