Problem with auto installer

[Lokonli]

I would try to reinstall docker:

Code: Select all

sudo apt-get remove docker docker-engine docker.io containerd runc
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh

And then first try the hello-world app:

Code: Select all

sudo docker run hello-world

[danman87]

ahh i fixed it by doing the ''sudo apt --fix-broken install'' command

here the output:

pi@raspberrypi:~$ sudo docker images | grep apache
php apache fabd924a2602 2 weeks ago 300MB

pi@raspberrypi:~$ sudo journalctl -xe
--
-- The unit UNIT has successfully entered the 'dead' state.
Apr 15 22:35:17 raspberrypi dockerd[20968]: time="2020-04-15T22:35:17.440820362+02:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Apr 15 22:35:17 raspberrypi systemd[1]: var-lib-docker-overlay2-check\x2doverlayfs\x2dsupport900759855-merged.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit var-lib-docker-overlay2-check\x2doverlayfs\x2dsupport900759855-merged.mount has successfully entered the 'dead' state.
Apr 15 22:35:17 raspberrypi dockerd[20968]: time="2020-04-15T22:35:17.993878377+02:00" level=warning msg="Your kernel does not support swap memory limit"
Apr 15 22:35:18 raspberrypi dockerd[20968]: time="2020-04-15T22:35:18.001165312+02:00" level=warning msg="Your kernel does not support cgroup cfs period"
Apr 15 22:35:18 raspberrypi dockerd[20968]: time="2020-04-15T22:35:18.001628308+02:00" level=warning msg="Your kernel does not support cgroup cfs quotas"
Apr 15 22:35:18 raspberrypi dockerd[20968]: time="2020-04-15T22:35:18.002204302+02:00" level=warning msg="Your kernel does not support cgroup rt period"
Apr 15 22:35:18 raspberrypi dockerd[20968]: time="2020-04-15T22:35:18.002920296+02:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Apr 15 22:35:18 raspberrypi dockerd[20968]: time="2020-04-15T22:35:18.003357292+02:00" level=warning msg="Unable to find cpuset cgroup in mounts"
Apr 15 22:35:18 raspberrypi dockerd[20968]: time="2020-04-15T22:35:18.003903287+02:00" level=warning msg="mountpoint for pids not found"
Apr 15 22:35:18 raspberrypi dockerd[20968]: time="2020-04-15T22:35:18.087796532+02:00" level=info msg="Loading containers: start."
Apr 15 22:35:22 raspberrypi systemd-udevd[20983]: Using default interface naming scheme 'v240'.
Apr 15 22:35:24 raspberrypi avahi-daemon[20832]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Apr 15 22:35:24 raspberrypi kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Apr 15 22:35:24 raspberrypi avahi-daemon[20832]: New relevant interface docker0.IPv4 for mDNS.
Apr 15 22:35:24 raspberrypi avahi-daemon[20832]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Apr 15 22:35:25 raspberrypi dockerd[20968]: time="2020-04-15T22:35:25.391925210+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address
Apr 15 22:35:27 raspberrypi dockerd[20968]: time="2020-04-15T22:35:27.420703220+02:00" level=info msg="Loading containers: done."
Apr 15 22:35:28 raspberrypi systemd[464]: var-lib-docker-overlay2-opaque\x2dbug\x2dcheck950963431-merged.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit UNIT has successfully entered the 'dead' state.
Apr 15 22:35:28 raspberrypi systemd[1]: var-lib-docker-overlay2-opaque\x2dbug\x2dcheck950963431-merged.mount: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit var-lib-docker-overlay2-opaque\x2dbug\x2dcheck950963431-merged.mount has successfully entered the 'dead' state.
Apr 15 22:35:30 raspberrypi dockerd[20968]: time="2020-04-15T22:35:30.250776234+02:00" level=info msg="Docker daemon" commit=afacb8b graphdriver(s)=overlay2 ve
Apr 15 22:35:30 raspberrypi dockerd[20968]: time="2020-04-15T22:35:30.268169081+02:00" level=info msg="Daemon has completed initialization"
Apr 15 22:35:31 raspberrypi systemd[1]: Started Docker Application Container Engine.
-- Subject: A start job for unit docker.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit docker.service has finished successfully.
--
-- The job identifier is 2687.
Apr 15 22:35:31 raspberrypi sudo[20936]: pam_unix(sudo:session): session closed for user root
Apr 15 22:35:31 raspberrypi dockerd[20968]: time="2020-04-15T22:35:31.826611377+02:00" level=info msg="API listen on /var/run/docker.sock"
Apr 15 22:35:36 raspberrypi sudo[21122]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/docker images
Apr 15 22:35:36 raspberrypi sudo[21122]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Apr 15 22:35:40 raspberrypi sudo[21122]: pam_unix(sudo:session): session closed for user root
Apr 15 22:37:02 raspberrypi sudo[21137]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xe
Apr 15 22:37:02 raspberrypi sudo[21137]: pam_unix(sudo:session): session opened for user root by pi(uid=0)

[danman87]

ok reinstalled it:

pi@raspberrypi:~$ sudo sh get-docker.sh
# Executing docker install script, commit: 442e66405c304fa92af8aadaa1d9b31bf4b0ad94
Warning: the "docker" command appears to already exist on this system.

If you already have Docker installed, this script can cause trouble, which is
why we're displaying this warning and provide the opportunity to cancel the
installation.

If you installed the current Docker package using this script and are using it
again to update Docker, you can safely ignore this message.

You may press Ctrl+C now to abort this script.
+ sleep 20
+ sh -c apt-get update -qq >/dev/null
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ 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)
+ sh -c echo "deb [arch=armhf] https://download.docker.com/linux/raspbian buster stable" > /etc/apt/sources.list.d/docker.list
+ sh -c apt-get update -qq >/dev/null
+ [ -n ]
+ sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
+ sh -c docker version
Client: Docker Engine - Community
Version: 19.03.8
API version: 1.40
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:35:24 2020
OS/Arch: linux/arm
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.8
API version: 1.40 (minimum version 1.12)
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:29:22 2020
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
If you would like to use Docker as a non-root user, you should now consider
adding your user to the "docker" group with something like:

sudo usermod -aG docker your-user

Remember that you will have to log out and back in for this to take effect!

WARNING: Adding a user to the "docker" group will grant the ability to run
containers which can be used to obtain root privileges on the
docker host.
Refer to https://docs.docker.com/engine/security ... ck-surface
for more information.
pi@raspberrypi:~$ sudo docker run hello-world
pi@raspberrypi:~$

when i go to the ip address of the pi on port 80 i get
Apache2 Debian Default Page
It works!

[Lokonli]

port 80 is your 'normal' apache server. If you follow the manual install you will use that one.

Maybe first check that docker is indeed working correctly:

Code: Select all

sudo docker run hello-world

[danman87]

sudo docker run hello-world

doesn't give anything back...

pi@raspberrypi:~$ sudo docker run hello-world
pi@raspberrypi:~$

[Lokonli]

That's not ok ...
I'm afraid docker crashed again.

Or we give it a last try by following this:
https://withblue.ink/2019/07/13/yes-you ... pbian.html

or you have to follow the instructions in the manual install method.

[danman87]

could it be the ip adres? i saw that it got 172.17.0.1??

[Lokonli]

Maybe it's a problem with the hello-world package for arm.
Just to be sure, can you test docker in the test folder:

sudo docker build .



Sent from my SM-A320FL using Tapatalk

[danman87]

Hi Lokonli,

i get this in the test folder:

pi@raspberrypi:~/test$ sudo docker build .
Sending build context to Docker daemon 2.048kB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN ls
---> Running in 4f594ea24d15
The command '/bin/sh -c ls' returned a non-zero code: 139

[danman87]

i also did all the steps from the withblue.ink site you mentioned.
but it still doesn't work:

pi@raspberrypi:~$ sudo docker run hello-world
pi@raspberrypi:~$ cd ~/test
pi@raspberrypi:~/test$ sudo docker build .
Sending build context to Docker daemon 2.048kB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN ls
---> Running in 21e5ebf13e4c
The command '/bin/sh -c ls' returned a non-zero code: 139
pi@raspberrypi:~/test$

[Lokonli]

i also did all the steps from the withblue.ink site you mentioned.
but it still doesn't work:

pi@raspberrypi:~$ sudo docker run hello-world
pi@raspberrypi:~$ cd ~/test
pi@raspberrypi:~/test$ sudo docker build .
Sending build context to Docker daemon 2.048kB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN ls
---> Running in 21e5ebf13e4c
The command '/bin/sh -c ls' returned a non-zero code: 139
pi@raspberrypi:~/test$

I'm out of ideas.

I just updated my spare Raspberry PI to Buster. Installed Docker as described above. Everything works ok.

You have Pi 3?

I propose you switch to the manual install method ...

[danman87]

it's:
Raspberry Pi Model B Plus Rev 1.2

[danman87]

is this pi to old maybe?

[danman87]

it's working with the manual install!

thank you for you're help!

[Lokonli]

ok, well done Thanks for the update.