Docker-CE need updating for raspbian buster

nlt6444 commented 5 years ago

[x] This is a bug report
[ ] This is a feature request
[ x] I searched existing issues before opening this one

Expected behavior

Successful install

Actual behavior

Docker-CE is unavailable for raspbian buster. I would to request an update to the application.

Steps to reproduce the behavior

Install the following prerequisites.

sudo apt-get install apt-transport-https ca-certificates software-properties-common -y b. Download and install Docker.

curl -fsSL get.docker.com -o get-docker.sh && sh get-docker.sh c. Give the ‘pi’ user the ability to run Docker.

sudo usermod -aG docker pi d. Import Docker CPG key.

sudo curl https://download.docker.com/linux/raspbian/gpg e. Setup the Docker Repo.

vim /etc/apt/sources.list Add the following line and save:

deb https://download.docker.com/linux/raspbian/ stretch stable

Floppy commented 5 years ago

This is definitely a problem, because as noted in #545, the docker.io package in the default raspbian buster repo isn't working at all either.

EasternPA commented 5 years ago

Edit: Removing prior comment. I was an idiot. I mistakenly specified [arch=amd64] in /etc/apt/sources.list. I changed arch to armhf and docker-ce showed right up and installed properly.

garyng commented 5 years ago

Any updates on this?

Qarasique commented 5 years ago

Confirm, cant install on raspbian buster

hminaya commented 5 years ago

Any way to manually install?

marklagendijk commented 5 years ago

The docker packages are included in Raspbian buster by default. You can install with sudo apt-get install docker.io docker-compose. Restart after installation.

Update: Although you can install docker and docker-compose, you get the error ERROR: for SERVICE_NAME Cannot start service SERVICE_NAME: unable to find "net_prio" in controller set: unknown when trying to start any image. As described here this is because of an outdated version of containerd in the docker-io package.

kolektiv commented 5 years ago

I believe that the docker.io packages in the repo are not recommended by docker, according to the docker install instructions.

On 29 Jun 2019, at 18:50, Mark Lagendijk notifications@github.com wrote:

The docker packages are included in Raspbian buster by default. You can install with sudo apt-get install docker.io docker-compose.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

garyng commented 5 years ago

Any way to manually install?

I manually edited the install script from get.docker.com to force it to download the stretch version of docker. Maybe give it a try?

hminaya commented 5 years ago

@garyng how did it work out for you? All good with the containers?

garyng commented 5 years ago

@hminaya seems pretty stable ... for now

MBlokhuijzen commented 5 years ago

@garyng could you maybe share the the script? I'm not entirely sure what to edit in the script

MBlokhuijzen commented 5 years ago

Found a way to do it.

Edit /etc/apt/sources.list.d/docker.list
Change line to: deb [arch=armhf] https://download.docker.com/linux/raspbian stretch stable

After that I'm able to use Docker

andresbono commented 5 years ago

I confirm it works for now. Oneliner to install it on raspbian buster:

curl -sL get.docker.com | sed 's/9)/10)/' | sh

kasprzakdanielt commented 5 years ago

I confirm it works for now. Oneliner to install it on raspbian buster:
curl -sL get.docker.com | sed 's/9)/10)/' | sh

still just a workaround, not a fix tho

notogawa commented 5 years ago

@MBlokhuijzen, it works on pi3. On pi0, it fails with illegal instruction.

notogawa commented 5 years ago

I think there is no docker-ce package and workaround works on pi0(armv6) raspbian buster.

notogawa commented 5 years ago

result	docker-ce package	raspbian	device	issue/reason
works	18.09.0\~3-0\~raspbian-stretch	stretch	pi3
fails	18.09.0\~3-0\~raspbian-stretch	stretch	pi0	https://github.com/docker/for-linux/issues/681
works	18.06.1\~ce\~3-0\~raspbian	stretch	pi3
works	18.06.1\~ce\~3-0\~raspbian	stretch	pi0
works	18.09.0\~3-0\~raspbian-stretch	buster	pi3
fails	18.09.0\~3-0\~raspbian-stretch	buster	pi0	illegal instruction
fails	18.06.1\~ce\~3-0\~raspbian	buster	pi3	https://github.com/docker/for-linux/issues/545

xenosathl commented 5 years ago

For more detailed explanation of workaround proposed by @andresbono

Find do_install function. (in my scenario line 205.)
Find switch for $lsb_dist (in my scenario 280.) and proceed to 'debian|raspbian' case.
Inside sub-switch $dist_version (in my scenario 293.) add another case like:
```
case "$dist_version" in
10)
    dist_version="stretch"
     ;;
# [...]
```

lowdef commented 5 years ago

I confirm it works for now. Oneliner to install it on raspbian buster:
curl -sL get.docker.com | sed 's/9)/10)/' | sh

does not work here on RPi 3 B+. Pristine install from recent NOOBS, installs buster:

pi@raspberrypi:~/src/docker $ curl -sL get.docker.com | sed 's/9)/10)/' | sh
# Executing docker install script, commit: 2f4ae48
+ sudo -E sh -c apt-get update -qq >/dev/null
E: The repository 'https://download.docker.com/linux/raspbian 10 Release' does not have a Release file.

post edit: It works if you make sure the repository config is clean, see the answer from @caio below.

theDiverDK commented 5 years ago

The oneline does not work on Raspberry PI 3b either.

Get the same error as @lowdef :-(

caio commented 5 years ago

@lowdef & @theDiverDK - The error you are getting is because the script is resuming from a partial state. If you drop the repository config, the curl|sed|sh workaround you're trying should work:

sudo rm /etc/apt/sources.list.d/docker.list;
curl -sL get.docker.com | sed 's/9)/10)/' | sh

(Or just adjust the file to point to stretch instead of 10, as mentioned @ https://github.com/docker/for-linux/issues/709#issuecomment-506981764)

theDiverDK commented 5 years ago

thanks @caio

It sure does work now, thanks :)

brtwrst commented 5 years ago

I got it installed without problems by downloading the most recent .deb files for containerd.io, docker-ce-cli and docker-ce from here https://download.docker.com/linux/debian/dists/buster/pool/stable/armhf/ and installing them in that order with sudo dpkg -i <deb-file>

System: Raspberry PI 4 Latest Raspbian Buster deb files: containerd.io_1.2.6-3_armhf.deb docker-ce_18.09.7~3-0~debian-buster_armhf.deb docker-ce-cli_18.09.7~3-0~debian-buster_armhf.deb

d11wtq commented 5 years ago

Following the manual instructions and using the latest edge instead of stable works for me on buster https://docs.docker.com/install/linux/docker-ce/binaries/#install-daemon-and-client-binaries-on-linux

sirius1024 commented 5 years ago

It worked with @caio 's way.

notogawa commented 5 years ago

please report which device you use.

sirius1024 commented 5 years ago

RPi 3 Model B (not plus).

theDiverDK commented 5 years ago

@caio 's way worked for me as well on a Raspberry Pi 3b (not plus)

Now i am just waiting for my Pi4 4gb :)

NobodyXu commented 5 years ago

I installed docker-ce on raspberry pi 3B+, raspbian buster, by manually adding /etc/apt/sources.list.d/docker-ce.list:

deb https://download.docker.com/linux/debian buster stable
deb-src https://download.docker.com/linux/debian buster stable

and adding the key using add-key https://download.docker.com/linux/debian/gpg.

Then apt update && apt install -y —no-install-recommends docker-ce docker-ce-cli containerd.io works for me.

Emitting —no-install-recommends will cause aufs-dkms to be installed of which the compilation failed for me.

biodrone commented 5 years ago

@caio that works on my Pi4, thanks :)

sebns commented 5 years ago

@NobodyXu 's solution worked for me.

I just followed the instructions from docker.com for arch=armhf, except that I added the option --no-install-recommends:

$ sudo apt-get install --no-install-recommends docker-ce docker-ce-cli containerd.io

notogawa commented 5 years ago

Is there no way to success on pi0?

haxmanster commented 5 years ago

sudo apt-get install --no-install-recommends docker-ce docker-ce-cli containerd.io

This very helpfull on Rpi4 rasbian buster

SiM22 commented 5 years ago

I got it running with:

sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

but then docker-cli was not installed and installing docker-ce-cli removes this version of docker-ce. in a nutshell this is what i did to get it running

add this line

pi@raspberrypi:~ $ sudo cat /etc/apt/sources.list.d/docker.list
deb [arch=armhf] https://download.docker.com/linux/raspbian stretch edge

then the following in this order

sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian
sudo apt-get install docker-ce-cli
apt-get download docker-ce=18.06.1~ce~3-0~raspbian
sudo dpkg -i docker-ce_18.06.1~ce~3-0~raspbian_armhf.deb

first install docker then latest version of the cli which overwrites the version of doker-ce installing v.18.06.1 again overwrites the cli tool so i downloaded the package manually and then installed with dpkg.

and now i have a working docker with no errors of start failures

pi@raspberrypi:~ $ docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.19.50+
Operating System: Raspbian GNU/Linux 10 (buster)
OSType: linux
Architecture: armv6l
CPUs: 1
Total Memory: 432.7MiB
Name: raspberrypi
ID: PM6D:UG7E:OJ7F:EEW5:7AYK:QS5E:GZOA:DAV6:GBTR:5B5I:IQOA:MVU7
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpuset support

SiM22 commented 5 years ago

Update. I get it to install but it throws another error about net_prio. Hopefully there will be a release for buster soon

NobodyXu commented 5 years ago

@SiM22 DId you forget to also install containerd.io? If I recalled right, that is the actual backend docker used to create container. It manipulate namespace, do the mounting kind of stuff.

Edit:

If you use apt cache show docker, you will find out that docker depends on containerd.io.

thaJeztah commented 5 years ago

related issues and PR's;

https://github.com/moby/moby/issues/39417 Is 'docker' available via curl script for Buster / Debian 10?
https://github.com/docker/docker-ce-packaging/pull/349 Add Raspbian buster
https://github.com/docker/docker-install/pull/126 Add support for Debian Buster
https://github.com/docker/docker-ce-packaging/pull/361 [19.03 backport] Add Raspbian buster

theDiverDK commented 5 years ago

curl -sL get.docker.com | sed 's/9)/10)/' | sh

Works in Pi4 as well :)

logopk commented 5 years ago

Will docker work if installed before dist-upgrade (apt.list with stretch)?

Thanks in advance.

thaJeztah commented 5 years ago

Nightly builds are now available for raspbian buster; https://download.docker.com/linux/raspbian/dists/buster/pool/nightly/armhf/

notogawa commented 5 years ago

Nightly builds are now available for raspbian buster; https://download.docker.com/linux/raspbian/dists/buster/pool/nightly/armhf/

I try to install that with 2019-06-20-raspbian-buster-lite.img on pi0.

$ sudo apt-get update --allow-releaseinfo-change
$ sudo apt-get update
$ sudo apt-get upgrade -y
$ sudo reboot

$ sudo nano -w /etc/apt/sources.list.d/docker.list
+deb [arch=armhf] https://download.docker.com/linux/raspbian buster nightly
$ wget -O- https://download.docker.com/linux/raspbian/gpg | sudo apt-key add -
$ sudo apt-get update
$ sudo apt-cache show docker-ce | grep Version
Version: 5:0.0.0-20190708210316-d3539bd-0~raspbian-buster
$ sudo apt-get install docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 docker-ce : Depends: containerd.io (>= 1.2.2-3) but it is not installable
             Recommends: aufs-tools but it is not going to be installed
             Recommends: cgroupfs-mount but it is not going to be installed or
                         cgroup-lite but it is not installable
             Recommends: git but it is not going to be installed
             Recommends: pigz but it is not going to be installed
             Recommends: libltdl7 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
$ sudo apt-cache search containerd.io

I use containerd.io in raspbian docker stretch repository.

$ sudo nano -w /etc/apt/sources.list.d/docker.list
 deb [arch=armhf] https://download.docker.com/linux/raspbian buster nightly
+deb [arch=armhf] https://download.docker.com/linux/raspbian stretch stable
$ sudo apt-get update
$ sudo apt-cache search containerd.io
containerd.io - An open and reliable container runtime
$ sudo apt-cache search containerd.io
$ sudo apt-cache show containerd.io | grep Version
Version: 1.2.6-3
Version: 1.2.5-1
Version: 1.2.4-1
Version: 1.2.2-3
Version: 1.2.2-1
Version: 1.2.0-1
Version: 1.2.0~rc.2-1
Version: 1.2.0~rc.0-1
Version: 1.2.0~beta.2-1
$ sudo apt-cache show docker-ce | grep Version
Version: 5:18.09.0~3-0~raspbian-stretch
Version: 5:0.0.0-20190708210316-d3539bd-0~raspbian-buster
Version: 18.06.3~ce~3-0~raspbian
Version: 18.06.2~ce~3-0~raspbian
Version: 18.06.1~ce~3-0~raspbian
Version: 18.06.0~ce~3-0~raspbian
Version: 18.03.1~ce-0~raspbian
Version: 18.03.0~ce-0~raspbian
Version: 17.12.1~ce-0~raspbian
Version: 17.12.0~ce-0~raspbian
Version: 17.09.1~ce-0~raspbian
Version: 17.09.0~ce-0~raspbian
$ sudo nano -w /etc/apt/preferences.d/docker.pref
+Package: docker-ce
+Pin: version 5:0.0.0-20190708210316-d3539bd-0~raspbian-buster
+Pin-Priority: 990
+
+Package: docker-ce-cli
+Pin: version 5:0.0.0-20190708210316-d3539bd-0~raspbian-buster
+Pin-Priority: 990
$ sudo apt-get install docker-ce -y --no-install-recommends
(snip.)
Job for docker.service canceled.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Wed 2019-07-10 02:05:15 BST; 1s ago
     Docs: https://docs.docker.com
  Process: 1087 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=killed, signal=TERM)
 Main PID: 1087 (code=killed, signal=TERM)

Jul 10 02:05:14 ntgwpi0 systemd[1]: Starting Docker Application Container Engine...
Jul 10 02:05:15 ntgwpi0 systemd[1]: docker.service: Main process exited, code=killed, status=15/TERM
Jul 10 02:05:15 ntgwpi0 systemd[1]: docker.service: Succeeded.
Jul 10 02:05:15 ntgwpi0 systemd[1]: Stopped Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-5+rpi1) ...
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Wed 2019-07-10 02:05:15 BST; 1min 53s ago
     Docs: https://docs.docker.com
 Main PID: 1087 (code=killed, signal=TERM)

Jul 10 02:05:14 ntgwpi0 systemd[1]: Starting Docker Application Container Engine...
Jul 10 02:05:15 ntgwpi0 systemd[1]: docker.service: Main process exited, code=killed, status=15/TERM
Jul 10 02:05:15 ntgwpi0 systemd[1]: docker.service: Succeeded.
Jul 10 02:05:15 ntgwpi0 systemd[1]: Stopped Docker Application Container Engine.
$ systemctl status containerd.service
● containerd.service - containerd container runtime
   Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled)
   Active: failed (Result: core-dump) since Wed 2019-07-10 02:05:15 BST; 2min 11s ago
     Docs: https://containerd.io
 Main PID: 1086 (code=dumped, signal=SEGV)

Jul 10 02:05:14 ntgwpi0 systemd[1]: Starting containerd container runtime...
Jul 10 02:05:14 ntgwpi0 systemd[1]: Started containerd container runtime.
Jul 10 02:05:15 ntgwpi0 systemd[1]: containerd.service: Main process exited, code=dumped, status=11/SEGV
Jul 10 02:05:15 ntgwpi0 systemd[1]: containerd.service: Failed with result 'core-dump'.
$ sudo /usr/bin/containerd
Segmentation fault

This problem is the same as https://github.com/docker/for-linux/issues/681 It is required containerd.io package which works on pi0(armv6l).

d11wtq commented 5 years ago

Same issue here (Raspberry Pi 4). It appears containerd.io is currently missing from the repository.

jasmas commented 5 years ago

So I was following the path of updating/installing docker-ce as well because that was the norm on stretch, but fwiw:

pi@raspberrypi:~ $ sudo apt install docker-compose
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  cgroupfs-mount docker.io golang-docker-credential-helpers libintl-perl libintl-xs-perl libmodule-find-perl libmodule-scandeps-perl libnspr4 libnss3 libproc-processtable-perl libsecret-1-0 libsecret-common libsort-naturally-perl libterm-readkey-perl needrestart
  python3-cached-property python3-certifi python3-chardet python3-docker python3-dockerpty python3-dockerpycreds python3-docopt python3-idna python3-jsonschema python3-requests python3-texttable python3-urllib3 python3-websocket python3-yaml runc tini
Suggested packages:
  docker-doc aufs-tools btrfs-progs debootstrap rinse xfsprogs zfs-fuse | zfsutils needrestart-session | libnotify-bin iucode-tool python-jsonschema-doc python3-openssl python3-socks
The following NEW packages will be installed:
  cgroupfs-mount docker-compose docker.io golang-docker-credential-helpers libintl-perl libintl-xs-perl libmodule-find-perl libmodule-scandeps-perl libnspr4 libnss3 libproc-processtable-perl libsecret-1-0 libsecret-common libsort-naturally-perl libterm-readkey-perl
  needrestart python3-cached-property python3-certifi python3-chardet python3-docker python3-dockerpty python3-dockerpycreds python3-docopt python3-idna python3-jsonschema python3-requests python3-texttable python3-urllib3 python3-websocket python3-yaml runc tini
0 upgraded, 32 newly installed, 0 to remove and 0 not upgraded.
Need to get 44.3 MB/44.3 MB of archives.
After this operation, 192 MB of additional disk space will be used.
Do you want to continue? [Y/n]

jasmas commented 5 years ago

On the pi0, net_prio not compiled into the kernel is still a problem with the updated buster systemd, but recompiling the kernel would appear to be the current workaround until the upstream fixes trickle down.

thaJeztah commented 5 years ago

Ah, good one; changes for the containerd.io package may not be in place yet; I'll have a look at that one

cgc007 commented 5 years ago

@SiM22's method of installing docker worked for me on my fresh install of debian buster lite on my rPi4. The install script never completes correctly, citing:

E: Failed to fetch https://apt.dockerproject.org/repo/dists/raspbian-buster/InRelease 403 Forbidden [IP: 13.249.142.105 443]

E: The repository 'https://apt.dockerproject.org/repo raspbian-buster InRelease' is not signed.

ItalyPaleAle commented 5 years ago

Trying to use Stretch packages on Raspbian Buster (RPi 2), it fails for me while compiling aufs:

$ sudo apt install docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  aufs-dkms aufs-tools cgroupfs-mount containerd.io dkms docker-ce-cli git git-man liberror-perl libltdl7 pigz
  raspberrypi-kernel-headers
Suggested packages:
  aufs-dev python3-apport menu git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb
  git-cvs git-mediawiki git-svn
The following NEW packages will be installed:
  aufs-dkms aufs-tools cgroupfs-mount containerd.io dkms docker-ce docker-ce-cli git git-man liberror-perl
  libltdl7 pigz raspberrypi-kernel-headers
0 upgraded, 13 newly installed, 0 to remove and 0 not upgraded.
Need to get 63.4 MB of archives.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.19.57-v7+
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.19.57-v7l+
Setting up containerd.io (1.2.6-3) ...
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Setting up libltdl7:armhf (2.4.6-9) ...
Setting up docker-ce-cli (5:18.09.0~3-0~raspbian-stretch) ...
Setting up aufs-dkms (4.19+20190211-1) ...
Loading new aufs-4.19+20190211 DKMS files...
It is likely that 4.19.57-v7+ belongs to a chroot's host
Building for 4.19.57+, 4.19.57-v7+ and 4.19.57-v7l+
Building initial module for 4.19.57+
Error! Bad return status for module build on kernel: 4.19.57+ (armv7l)
Consult /var/lib/dkms/aufs/4.19+20190211/build/make.log for more information.
dpkg: error processing package aufs-dkms (--configure):
 installed aufs-dkms package post-installation script subprocess returned error exit status 10
Setting up pigz (2.4-1) ...
Setting up git-man (1:2.20.1-2) ...
Setting up cgroupfs-mount (1.4) ...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "en_US.UTF-8",
    LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Setting up aufs-dkms (4.19+20190211-1) ...
Removing old aufs-4.19+20190211 DKMS files...

------------------------------
Deleting module version: 4.19+20190211
completely from the DKMS tree.
------------------------------
Done.
Loading new aufs-4.19+20190211 DKMS files...
It is likely that 4.19.57-v7+ belongs to a chroot's host
Building for 4.19.57+, 4.19.57-v7+ and 4.19.57-v7l+
Building initial module for 4.19.57+
Error! Bad return status for module build on kernel: 4.19.57+ (armv7l)
Consult /var/lib/dkms/aufs/4.19+20190211/build/make.log for more information.
dpkg: error processing package aufs-dkms (--configure):
 installed aufs-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 aufs-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ cat /var/lib/dkms/aufs/4.19+20190211/build/make.log
DKMS make.log for aufs-4.19+20190211 for kernel 4.19.57+ (armv7l)
Fri Jul 12 19:36:30 BST 2019
make: Entering directory '/var/lib/dkms/aufs/4.19+20190211/build'
-I/var/lib/dkms/aufs/4.19+20190211/build/include -DCONFIG_AUFS_FS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_SBILIST
make -C /lib/modules/4.19.57+/build M=/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs EXTRA_CFLAGS="-I/var/lib/dkms/aufs/4.19+20190211/build/include -DCONFIG_AUFS_FS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_SBILIST" modules
make[1]: Entering directory '/usr/src/linux-headers-4.19.57+'
  CC [M]  /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.o
  CC [M]  /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/sbinfo.o
  CC [M]  /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.o
  CC [M]  /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.o
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:33,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/sbinfo.c:23:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:134:2: error: unknown type name 'vfs_readf_t'
  vfs_readf_t  si_xread;
  ^~~~~~~~~~~
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:135:2: error: unknown type name 'vfs_writef_t'
  vfs_writef_t  si_xwrite;
  ^~~~~~~~~~~~
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/sbinfo.c:23:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:243:20: error: unknown type name 'vfs_readf_t'
 ssize_t xino_fread(vfs_readf_t func, struct file *file, void *buf, size_t size,
                    ^~~~~~~~~~~
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:33,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.c:27:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:134:2: error: unknown type name 'vfs_readf_t'
  vfs_readf_t  si_xread;
  ^~~~~~~~~~~
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:135:2: error: unknown type name 'vfs_writef_t'
  vfs_writef_t  si_xwrite;
  ^~~~~~~~~~~~
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:245:21: error: unknown type name 'vfs_writef_t'; did you mean 'pte_write'?
 ssize_t xino_fwrite(vfs_writef_t func, struct file *file, void *buf,
                     ^~~~~~~~~~~~
                     pte_write
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.c:27:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:243:20: error: unknown type name 'vfs_readf_t'; did you mean 'key_ref_t'?
 ssize_t xino_fread(vfs_readf_t func, struct file *file, void *buf, size_t size,
                    ^~~~~~~~~~~
                    key_ref_t
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:33,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:134:2: error: unknown type name 'vfs_readf_t'
  vfs_readf_t  si_xread;
  ^~~~~~~~~~~
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:135:2: error: unknown type name 'vfs_writef_t'
  vfs_writef_t  si_xwrite;
  ^~~~~~~~~~~~
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:245:21: error: unknown type name 'vfs_writef_t'; did you mean 'key_ref_t'?
 ssize_t xino_fwrite(vfs_writef_t func, struct file *file, void *buf,
                     ^~~~~~~~~~~~
                     key_ref_t
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:33,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:134:2: error: unknown type name 'vfs_readf_t'
  vfs_readf_t  si_xread;
  ^~~~~~~~~~~
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:135:2: error: unknown type name 'vfs_writef_t'
  vfs_writef_t  si_xwrite;
  ^~~~~~~~~~~~
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:46,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/sbinfo.c:23:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h: In function 'au_vm_prfile_set':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h:334:7: error: 'struct vm_area_struct' has no member named 'vm_prfile'; did you mean 'vm_file'?
  vma->vm_prfile = file;
       ^~~~~~~~~
       vm_file
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:243:20: error: unknown type name 'vfs_readf_t'
 ssize_t xino_fread(vfs_readf_t func, struct file *file, void *buf, size_t size,
                    ^~~~~~~~~~~
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:243:20: error: unknown type name 'vfs_readf_t'; did you mean 'key_ref_t'?
 ssize_t xino_fread(vfs_readf_t func, struct file *file, void *buf, size_t size,
                    ^~~~~~~~~~~
                    key_ref_t
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:245:21: error: unknown type name 'vfs_writef_t'; did you mean 'pte_write'?
 ssize_t xino_fwrite(vfs_writef_t func, struct file *file, void *buf,
                     ^~~~~~~~~~~~
                     pte_write
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:46,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.c:27:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h: In function 'au_vm_prfile_set':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h:334:7: error: 'struct vm_area_struct' has no member named 'vm_prfile'; did you mean 'vm_file'?
  vma->vm_prfile = file;
       ^~~~~~~~~
       vm_file
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:245:21: error: unknown type name 'vfs_writef_t'; did you mean 'key_ref_t'?
 ssize_t xino_fwrite(vfs_writef_t func, struct file *file, void *buf,
                     ^~~~~~~~~~~~
                     key_ref_t
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:46,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h: In function 'au_vm_prfile_set':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h:334:7: error: 'struct vm_area_struct' has no member named 'vm_prfile'; did you mean 'vm_file'?
  vma->vm_prfile = file;
       ^~~~~~~~~
       vm_file
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:46,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h: In function 'au_vm_prfile_set':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h:334:7: error: 'struct vm_area_struct' has no member named 'vm_prfile'; did you mean 'vm_file'?
  vma->vm_prfile = file;
       ^~~~~~~~~
       vm_file
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:57,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/sbinfo.c:23:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h: In function 'vfsub_update_time':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h:233:9: error: implicit declaration of function 'update_time'; did you mean 'file_update_time'? [-Werror=implicit-function-declaration]
  return update_time(h_inode, ts, flags);
         ^~~~~~~~~~~
         file_update_time
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:303: /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/sbinfo.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:57,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h: In function 'vfsub_update_time':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h:233:9: error: implicit declaration of function 'update_time'; did you mean 'pte_same'? [-Werror=implicit-function-declaration]
  return update_time(h_inode, ts, flags);
         ^~~~~~~~~~~
         pte_same
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:57,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h: In function 'vfsub_update_time':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h:233:9: error: implicit declaration of function 'update_time'; did you mean 'pte_same'? [-Werror=implicit-function-declaration]
  return update_time(h_inode, ts, flags);
         ^~~~~~~~~~~
         pte_same
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:57,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.c:27:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h: In function 'vfsub_update_time':
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h:233:9: error: implicit declaration of function 'update_time'; did you mean 'file_update_time'? [-Werror=implicit-function-declaration]
  return update_time(h_inode, ts, flags);
         ^~~~~~~~~~~
         file_update_time
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:303: /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.o] Error 1
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:303: /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.o] Error 1
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:303: /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.o] Error 1
make[1]: *** [Makefile:1517: _module_/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.19.57+'
make: *** [Makefile:47: fs/aufs/aufs.ko] Error 2
make: Leaving directory '/var/lib/dkms/aufs/4.19+20190211/build'

NobodyXu commented 5 years ago

@ItalyPaleAle Try adding --no-install-recommends to apt as aufs is not a dependency of docker-ce, but merely a recommendation. With aufs not installed, this should work fine as I experienced the same problem and --no-install-recommends worked for me.

thestrid3r commented 5 years ago

Tried installing on Buster , Unable to start the docker service . Using this

curl -sL get.docker.com | sed 's/9)/10)/' | sh

● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-07-14 01:19:43 IST; 52s ago
     Docs: https://docs.docker.com
  Process: 20647 ExecStart=/usr/bin/dockerd -H unix:// (code=exited, status=1/FAILURE)
 Main PID: 20647 (code=exited, status=1/FAILURE)

Jul 14 01:19:41 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
Jul 14 01:19:43 raspberrypi systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Jul 14 01:19:43 raspberrypi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jul 14 01:19:43 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
Jul 14 01:19:43 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Jul 14 01:19:43 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 14 01:19:43 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
Jul 14 01:19:59 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Jul 14 01:19:59 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Jul 14 01:19:59 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.

MichaIng commented 5 years ago

Just for cross-reference: https://github.com/docker/docker-install/issues/125#issuecomment-511148912

Current upstream installer already has Buster integrated, but that has not yet been uploaded to: get.docker.com
Furthermore Raspbian Buster stable branch is not yet available, just nightly.
Using Raspbian Buster nightly branch works, but containerd.io is missing.
Using the Stretch stable branch additionally to pull containerd.io from seems to work.

Going with the above for me seems to be the best starting point to do testing on Raspbian Buster with. Using the Stretch stable version as some of you did above at least does not help for bug fixing and development of a Raspbian Buster Docker release, I guess 😉.

docker / for-linux