Garbage output on raspberry pi3 B/B+ when running and OCI container
up vote
0
down vote
favorite
I am running simple docker busybox container (converted to an OCI bundle) using docker-runC (https://github.com/opencontainers/runtime-spec) on a raspberry pi3, connected to a host via a UART terminal. The connection is done through pins 6-8-10 on the GPIO, using a UART to USB converter (C232HD USB to UART). Terminal settings : 115200 bps ,8 data / 1 stop bits, none parity and flow control.
I get garbage only when container internal process (in this case the Bourne shell prompt, but anything else will output the same garbage) outputs to the screen.
The problem won't occur when running the same container on imx7s WaRP7 device does (same architecture), or when connecting the raspberry pi3 with an HDMI cable to a screen.
Attached is a print screen of the garbage I see. The config.json file is the default (docker-runc spec) without changes.
I am running with process/env/TERM=xterm and process/terminal=true.
Does anyone have an idea why do I get this garbage only on raspberry pi3 and while using UART (not on other devices, and not when using HDMI) and can give me some direction on how to deal with this problem?
docker uart tty runc
edited Nov 8 at 3:53
Mat
1,25622029
asked Nov 7 at 17:05
user2917095
1
add a comment |
up vote
0
down vote
favorite
I am running simple docker busybox container (converted to an OCI bundle) using docker-runC (https://github.com/opencontainers/runtime-spec) on a raspberry pi3, connected to a host via a UART terminal. The connection is done through pins 6-8-10 on the GPIO, using a UART to USB converter (C232HD USB to UART). Terminal settings : 115200 bps ,8 data / 1 stop bits, none parity and flow control.
I get garbage only when container internal process (in this case the Bourne shell prompt, but anything else will output the same garbage) outputs to the screen.
The problem won't occur when running the same container on imx7s WaRP7 device does (same architecture), or when connecting the raspberry pi3 with an HDMI cable to a screen.
Attached is a print screen of the garbage I see. The config.json file is the default (docker-runc spec) without changes.
I am running with process/env/TERM=xterm and process/terminal=true.
Does anyone have an idea why do I get this garbage only on raspberry pi3 and while using UART (not on other devices, and not when using HDMI) and can give me some direction on how to deal with this problem?
docker uart tty runc
edited Nov 8 at 3:53
Mat
1,25622029
asked Nov 7 at 17:05
user2917095
1
raspberrypi.stackexchange.com
– Mat
Nov 8 at 6:48
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am running simple docker busybox container (converted to an OCI bundle) using docker-runC (https://github.com/opencontainers/runtime-spec) on a raspberry pi3, connected to a host via a UART terminal. The connection is done through pins 6-8-10 on the GPIO, using a UART to USB converter (C232HD USB to UART). Terminal settings : 115200 bps ,8 data / 1 stop bits, none parity and flow control.
I get garbage only when container internal process (in this case the Bourne shell prompt, but anything else will output the same garbage) outputs to the screen.
The problem won't occur when running the same container on imx7s WaRP7 device does (same architecture), or when connecting the raspberry pi3 with an HDMI cable to a screen.
Attached is a print screen of the garbage I see. The config.json file is the default (docker-runc spec) without changes.
I am running with process/env/TERM=xterm and process/terminal=true.
Does anyone have an idea why do I get this garbage only on raspberry pi3 and while using UART (not on other devices, and not when using HDMI) and can give me some direction on how to deal with this problem?
docker uart tty runc
edited Nov 8 at 3:53
Mat
1,25622029
asked Nov 7 at 17:05
user2917095
1
I am running simple docker busybox container (converted to an OCI bundle) using docker-runC (https://github.com/opencontainers/runtime-spec) on a raspberry pi3, connected to a host via a UART terminal. The connection is done through pins 6-8-10 on the GPIO, using a UART to USB converter (C232HD USB to UART). Terminal settings : 115200 bps ,8 data / 1 stop bits, none parity and flow control.
I get garbage only when container internal process (in this case the Bourne shell prompt, but anything else will output the same garbage) outputs to the screen.
The problem won't occur when running the same container on imx7s WaRP7 device does (same architecture), or when connecting the raspberry pi3 with an HDMI cable to a screen.
Attached is a print screen of the garbage I see. The config.json file is the default (docker-runc spec) without changes.
I am running with process/env/TERM=xterm and process/terminal=true.
Does anyone have an idea why do I get this garbage only on raspberry pi3 and while using UART (not on other devices, and not when using HDMI) and can give me some direction on how to deal with this problem?
docker uart tty runc
docker uart tty runc
edited Nov 8 at 3:53
Mat
1,25622029
asked Nov 7 at 17:05
user2917095
1
edited Nov 8 at 3:53
Mat
1,25622029
asked Nov 7 at 17:05
user2917095
1
edited Nov 8 at 3:53
Mat
1,25622029
edited Nov 8 at 3:53
Mat
1,25622029
edited Nov 8 at 3:53
Mat
1,25622029
1,25622029
asked Nov 7 at 17:05
user2917095
1
asked Nov 7 at 17:05
user2917095
1
asked Nov 7 at 17:05
user2917095
1
1
raspberrypi.stackexchange.com
– Mat
Nov 8 at 6:48
add a comment |
raspberrypi.stackexchange.com
– Mat
Nov 8 at 6:48
raspberrypi.stackexchange.com
– Mat
Nov 8 at 6:48
raspberrypi.stackexchange.com
– Mat
Nov 8 at 6:48
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53194352%2fgarbage-output-on-raspberry-pi3-b-b-when-running-and-oci-container%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
raspberrypi.stackexchange.com
– Mat
Nov 8 at 6:48