icy-garage-31078
09/15/2022, 5:42 PMdocker build
on a M1. The command runs, getting a couple steps in before it dies with a message of unexpected EOF
. If I immediately try to run the same command again, I instantly get the dread ...docker.sock. Is the docker daemon running
. I tried using DOCKER_HOST=<tcp://ip:2375> docker build ...
but this fails with the same error above after the build failedwide-mechanic-33041
09/15/2022, 5:58 PMicy-garage-31078
09/15/2022, 6:04 PMwide-mechanic-33041
09/15/2022, 6:08 PMicy-garage-31078
09/15/2022, 6:12 PMyarn run build
. Additionally, I've got the VM info in RD set to 24GB of Ram and 6 vCPUswide-mechanic-33041
09/15/2022, 6:13 PMicy-garage-31078
09/15/2022, 6:14 PMwide-mechanic-33041
09/15/2022, 6:14 PMicy-garage-31078
09/15/2022, 6:18 PMwide-mechanic-33041
09/15/2022, 6:20 PMrdctl shell
and you will be in the Alpine VM where the containers are running. challenge will be limited tooling in there by default. top is in there thoughtail -f /var/log/messages
to see what flies by as you do the buildicy-garage-31078
09/15/2022, 6:30 PMprocess '/sbin/getty -L 0 ttyS0 vt100' (pid 2047) exited. Scheduling for restart.
. I don't think it's related. I need to reboot RD and try a build again.alpine auth.err getty[24624]: tcgetattr: I/O error^M
. This is regardless of if the build is running or not and comes up every second or so. After running the build, I noticed a few different messages. When I first started, I saw /usr/local/bin/rancher-desktop-guestagent, pid 23857, exited with return code 0
, but after the build ran for a little it became /usr/local/bin/rancher-desktop-guestagent, pid 24620, terminated by signal 9
. While the build was running I saw the message Child command line: /usr/local/bin/cri-dockerd --container-runtime-endpoint unix:///run/cri-dockerd.sock --network-plugin=cni --cni-bin-dir=/usr/libexec/cni --cni-conf-dir=/etc/cni/net.d --cni-cache-dir=/var/lib/cni/cache
come up twice. Finally, right at the same time the docker build failed with the unexpected EOF
, I got Error: exit status 255
and went back to my normal shell. I ran rdctl shell
near immediately and it went right back in.wide-mechanic-33041
09/15/2022, 7:08 PMtop
icy-garage-31078
09/15/2022, 7:11 PMwide-mechanic-33041
09/15/2022, 7:28 PMicy-garage-31078
09/15/2022, 7:32 PMwide-mechanic-33041
09/15/2022, 7:35 PMicy-garage-31078
09/16/2022, 1:30 PM