Brewblox release 2020/10/19

Just decided to upgrade Raspberry Pi OS to Buster as suggested but the install process isn’t progressing as expected.

There’s something wrong when installing docker:

INFO Installing docker...
# Executing docker install script, commit: 26ff363bcf3b3f5a00498ac43694bf1c7d9ce16c
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ sudo -E sh -c curl -fsSL "https://download.docker.com/linux/raspbian/gpg" | apt-key add -qq - >/dev/null
Warning: apt-key output should not be parsed (stdout is not a terminal)
+ sudo -E sh -c echo "deb [arch=armhf] https://download.docker.com/linux/raspbian buster stable" > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c apt-get update -qq >/dev/null
+ [ -n ]
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
E: Sub-process /usr/bin/dpkg returned an error code (1)
Command 'curl -sL get.docker.com | sh' returned non-zero exit status 100.

Docker Service status:

Oct 27 20:23:10 raspberrypi systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Oct 27 20:23:10 raspberrypi systemd[1]: docker.service: Scheduled restart job, restart counter is at 4.
Oct 27 20:23:10 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
Oct 27 20:23:10 raspberrypi systemd[1]: **docker.service: Start request repeated too quickly.**
Oct 27 20:23:10 raspberrypi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Oct 27 20:23:10 raspberrypi systemd[1]: **Failed to start Docker Application Container Engine.**

Journal ($ journalctl -xe)

-- The job identifier is 2383.
Oct 27 20:23:10 raspberrypi systemd[1]: Listening on Docker Socket for the API.
-- Subject: A start job for unit docker.socket has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit docker.socket has finished successfully.
-- 
-- The job identifier is 2383.
Oct 27 20:23:10 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Oct 27 20:23:10 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Oct 27 20:23:10 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: A start job for unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit docker.service has finished with a failure.
-- 
-- The job identifier is 2320 and the job result is failed.
Oct 27 20:23:10 raspberrypi systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.

If memory serves, that’s a bug in the system service start after Docker was installed. Reboot your Pi, and the docker service should be running.

1 Like

@Bob_Steers, you have a good memory. That worked.

Here we go.

INFO       Skipped: docker install.
INFO       Skipped: adding pi to 'docker' group.
INFO       Extracting snapshot to /home/pi/brewblox directory...
mv: target '/home/pi/brewblox/' is not a directory
Command 'mv /tmp/tmpmzdm7gbp/brewblox/.[!.]* /tmp/tmpmzdm7gbp/brewblox/* /home/pi/brewblox/' returned non-zero exit status 1.

Just create the brewblox dir?

Does /home/pi/brewblox exist as file? never mind, looked at source, and we do check for that.

Otherwise, creating an empty brewblox/ dir should work, yes.

1 Like

Up and running.

Thanks for the quick response (as usual).

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.