Moby: docker-ce segmentation fault on Raspbian (v18.09.03)

[DutchessNicole]

Since two days ago docker will no longer start, after I updated the version that worked to
Version: 5:18.09.0~3-0~raspbian-stretch.
After that the docker daemon will no longer start.
strace -f dockerd reports
root@raspberrypi:~# strace -f dockerd execve("/usr/bin/dockerd", ["dockerd"], [/* 27 vars */]) = 0 brk(NULL) = 0x3b13000 uname({sysname="Linux", nodename="raspberrypi", ...}) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) mmap2(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6f6e000 access("/etc/ld.so.preload", R_OK) = 0 open("/etc/ld.so.preload", O_RDONLY|O_CLOEXEC) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=42, ...}) = 0 mmap2(NULL, 42, PROT_READ|PROT_WRITE, MAP_PRIVATE, 3, 0) = 0xb6f6d000 close(3) = 0 open("/usr/lib/arm-linux-gnueabihf/libarmmem.so", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\210\5\0\0004\0\0\0"..., 512) = 512 lseek(3, 20868, SEEK_SET) = 20868 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1000) = 1000 lseek(3, 20540, SEEK_SET) = 20540 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\3\f\1\22\4\24"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=21868, ...}) = 0 mmap2(NULL, 86080, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6f2b000 mprotect(0xb6f30000, 61440, PROT_NONE) = 0 mmap2(0xb6f3f000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4000) = 0xb6f3f000 close(3) = 0 munmap(0xb6f6d000, 42) = 0 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=28101, ...}) = 0 mmap2(NULL, 28101, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6f67000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libsystemd.so.0", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 512) = 512 lseek(3, 493188, SEEK_SET) = 493188 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1320) = 1320 lseek(3, 492748, SEEK_SET) = 492748 read(3, "A2\0\0\0aeabi\0\1(\0\0\0\0056\0\6\6\10\1\t\1\n\2\f\3\22\4\23"..., 51) = 51 fstat64(3, {st_mode=S_IFREG|0644, st_size=494508, ...}) = 0 mmap2(NULL, 499173, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6eb1000 mmap2(0xb6f28000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x76000) = 0xb6f28000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0dI\0\0004\0\0\0"..., 512) = 512 lseek(3, 125740, SEEK_SET) = 125740 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1560) = 1560 lseek(3, 90536, SEEK_SET) = 90536 read(3, "A.\0\0\0aeabi\0\1$\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\23\1\24"..., 47) = 47 fstat64(3, {st_mode=S_IFREG|0755, st_size=127300, ...}) = 0 mmap2(NULL, 164432, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6e88000 mprotect(0xb6e9e000, 61440, PROT_NONE) = 0 mmap2(0xb6ead000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x15000) = 0xb6ead000 mmap2(0xb6eaf000, 4688, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6eaf000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libseccomp.so.2", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\344\272\0\0004\0\0\0"..., 512) = 512 lseek(3, 139840, SEEK_SET) = 139840 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1040) = 1040 lseek(3, 139504, SEEK_SET) = 139504 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=140880, ...}) = 0 mmap2(NULL, 205044, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6e55000 mprotect(0xb6e6c000, 65536, PROT_NONE) = 0 mmap2(0xb6e7c000, 49152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0xb6e7c000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0@h\1\0004\0\0\0"..., 512) = 512 lseek(3, 1231820, SEEK_SET) = 1231820 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2880) = 2880 lseek(3, 1228284, SEEK_SET) = 1228284 read(3, "A.\0\0\0aeabi\0\1$\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\23\1\24"..., 47) = 47 fstat64(3, {st_mode=S_IFREG|0755, st_size=1234700, ...}) = 0 mmap2(NULL, 1303872, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6d16000 mprotect(0xb6e3f000, 65536, PROT_NONE) = 0 mmap2(0xb6e4f000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x129000) = 0xb6e4f000 mmap2(0xb6e52000, 9536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6e52000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libselinux.so.1", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0hN\0\0004\0\0\0"..., 512) = 512 lseek(3, 136448, SEEK_SET) = 136448 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1160) = 1160 lseek(3, 136088, SEEK_SET) = 136088 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=137608, ...}) = 0 mmap2(NULL, 208496, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6ce3000 mprotect(0xb6d03000, 65536, PROT_NONE) = 0 mmap2(0xb6d13000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x20000) = 0xb6d13000 mmap2(0xb6d15000, 3696, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6d15000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/librt.so.1", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0 \27\0\0004\0\0\0"..., 512) = 512 lseek(3, 25352, SEEK_SET) = 25352 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1280) = 1280 lseek(3, 24940, SEEK_SET) = 24940 read(3, "A.\0\0\0aeabi\0\1$\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\23\1\24"..., 47) = 47 fstat64(3, {st_mode=S_IFREG|0644, st_size=26632, ...}) = 0 mmap2(NULL, 90640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6ccc000 mprotect(0xb6cd2000, 61440, PROT_NONE) = 0 mmap2(0xb6ce1000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x5000) = 0xb6ce1000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/liblzma.so.5", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\230\"\0\0004\0\0\0"..., 512) = 512 lseek(3, 131848, SEEK_SET) = 131848 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1080) = 1080 lseek(3, 131500, SEEK_SET) = 131500 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=132928, ...}) = 0 mmap2(NULL, 197040, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6c9b000 mprotect(0xb6cbb000, 61440, PROT_NONE) = 0 mmap2(0xb6cca000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0xb6cca000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/usr/lib/arm-linux-gnueabihf/liblz4.so.1", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\300\32\0\0004\0\0\0"..., 512) = 512 lseek(3, 66052, SEEK_SET) = 66052 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1040) = 1040 lseek(3, 65748, SEEK_SET) = 65748 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=67092, ...}) = 0 mmap2(NULL, 131288, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6c7a000 mprotect(0xb6c8a000, 61440, PROT_NONE) = 0 mmap2(0xb6c99000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0xb6c99000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libgcrypt.so.20", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\\\0\0004\0\0\0"..., 512) = 512 lseek(3, 787796, SEEK_SET) = 787796 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1120) = 1120 lseek(3, 787437, SEEK_SET) = 787437 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\7\f\3\22\4\24"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=788916, ...}) = 0 mmap2(NULL, 853676, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6ba9000 mprotect(0xb6c65000, 65536, PROT_NONE) = 0 mmap2(0xb6c75000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xbc000) = 0xb6c75000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libgcc_s.so.1", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\200\321\0\0004\0\0\0"..., 512) = 512 lseek(3, 115292, SEEK_SET) = 115292 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1080) = 1080 lseek(3, 114944, SEEK_SET) = 114944 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=116372, ...}) = 0 mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6f65000 mmap2(NULL, 180536, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6b7c000 mprotect(0xb6b98000, 61440, PROT_NONE) = 0 mmap2(0xb6ba7000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b000) = 0xb6ba7000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libpcre.so.3", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0004\20\0\0004\0\0\0"..., 512) = 512 lseek(3, 426320, SEEK_SET) = 426320 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1040) = 1040 lseek(3, 426012, SEEK_SET) = 426012 read(3, "A,\0\0\0aeabi\0\1\"\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"..., 45) = 45 fstat64(3, {st_mode=S_IFREG|0644, st_size=427360, ...}) = 0 mmap2(NULL, 491604, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6b03000 mprotect(0xb6b6b000, 61440, PROT_NONE) = 0 mmap2(0xb6b7a000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x67000) = 0xb6b7a000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0P\t\0\0004\0\0\0"..., 512) = 512 lseek(3, 8680, SEEK_SET) = 8680 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1120) = 1120 lseek(3, 8328, SEEK_SET) = 8328 read(3, "A.\0\0\0aeabi\0\1$\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\23\1\24"..., 47) = 47 fstat64(3, {st_mode=S_IFREG|0644, st_size=9800, ...}) = 0 mmap2(NULL, 73912, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6af0000 mprotect(0xb6af2000, 61440, PROT_NONE) = 0 mmap2(0xb6b01000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0xb6b01000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/arm-linux-gnueabihf/libgpg-error.so.0", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0H\37\0\0004\0\0\0"..., 512) = 512 lseek(3, 61836, SEEK_SET) = 61836 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1120) = 1120 lseek(3, 61472, SEEK_SET) = 61472 read(3, "A.\0\0\0aeabi\0\1$\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\23\1\24"..., 47) = 47 fstat64(3, {st_mode=S_IFREG|0644, st_size=62956, ...}) = 0 mmap2(NULL, 127064, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb6ad0000 mprotect(0xb6adf000, 61440, PROT_NONE) = 0 mmap2(0xb6aee000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0xb6aee000 close(3) = 0 mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6f63000 set_tls(0xb6f634c0, 0xb6f63c88, 0xb6f72050, 0xb6f634c0, 0xb6f72050) = 0 mprotect(0xb6e4f000, 8192, PROT_READ) = 0 mprotect(0xb6aee000, 4096, PROT_READ) = 0 mprotect(0xb6b01000, 4096, PROT_READ) = 0 mprotect(0xb6ead000, 4096, PROT_READ) = 0 mprotect(0xb6b7a000, 4096, PROT_READ) = 0 mprotect(0xb6ba7000, 4096, PROT_READ) = 0 mprotect(0xb6c75000, 4096, PROT_READ) = 0 mprotect(0xb6c99000, 4096, PROT_READ) = 0 mprotect(0xb6cca000, 4096, PROT_READ) = 0 mprotect(0xb6ce1000, 4096, PROT_READ) = 0 mprotect(0xb6d13000, 4096, PROT_READ) = 0 mprotect(0xb6e7c000, 45056, PROT_READ) = 0 mprotect(0xb6f28000, 8192, PROT_READ) = 0 mprotect(0xb6f2b000, 20480, PROT_READ|PROT_WRITE) = 0 mprotect(0xb6f2b000, 20480, PROT_READ|PROT_EXEC) = 0 cacheflush(0xb6f2b000, 0xb6f30000, 0, 0x15, 0) = 0 mprotect(0xb6f3f000, 4096, PROT_READ) = 0 mprotect(0x1e44000, 16830464, PROT_READ) = 0 mprotect(0xb6f71000, 4096, PROT_READ) = 0 munmap(0xb6f67000, 28101) = 0 set_tid_address(0xb6f63068) = 2357 set_robust_list(0xb6f63070, 12) = 0 rt_sigaction(SIGRTMIN, {sa_handler=0xb6e8c2b0, sa_mask=[], sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0xb6d426c0}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {sa_handler=0xb6e8c390, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0xb6d426c0}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 ugetrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 brk(NULL) = 0x3b13000 brk(0x3b34000) = 0x3b34000 statfs("/sys/fs/selinux", 0xbea4e5cc) = -1 ENOENT (No such file or directory) statfs("/selinux", 0xbea4e5cc) = -1 ENOENT (No such file or directory) open("/proc/filesystems", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tr"..., 1024) = 310 read(3, "", 1024) = 0 close(3) = 0 access("/etc/selinux/config", F_OK) = -1 ENOENT (No such file or directory) --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x884a59} --- +++ killed by SIGSEGV +++ Segmentation fault

Similar to other reports all I get when running dockerd manually is "segmentation fault" and the logs report nothing interesting.

Docker version installed:
root@raspberrypi:~# docker version Client: Version: 18.09.0 API version: 1.39 Go version: go1.10.4 Git commit: 4d60db4 Built: Wed Nov 7 00:57:21 2018 OS/Arch: linux/arm Experimental: false Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Kernel info:
Linux raspberrypi 4.14.71+ #1145 Fri Sep 21 15:06:38 BST 2018 armv6l GNU/Linux

_Originally posted by @DutchessNicole in https://github.com/moby/moby/issues/29347#issuecomment-437581438_

[DutchessNicole]

@thaJeztah thank you for looking into it!

If necessary I can provide what little log info there is or traces.

thanks!

[thaJeztah]

Thanks for reporting!

Also reported in https://github.com/docker/compose/issues/6335

/cc @seemethere @andrewhsu

[lucaszanella]

Is there a way I can purge and install an older version for me to use docker for now? I really needed it.

[thaJeztah]

Sure; specify the version to install with apt https://askubuntu.com/a/92021, or use the instructions from this part of the installation docs https://docs.docker.com/install/linux/docker-ce/debian/#install-docker-ce-1

[lucaszanella]

Could you tell me which version does not have the problem?

[lucaszanella]

Ok it worked, I did

apt-cache madison docker-ce

and found the 16 version to be the latest and did

sudo apt-get install docker-ce=<VERSION_STRING>

[seemethere]

I think this is more about containerd than it is from dockerd, got a report from @fcrisciani that running containerd results in:

pi@us_rpi:~ $ /usr/bin/containerd
Illegal instruction

Currently investigating.

[seemethere]

@DutchessNicole Can you give me the output of your cat /proc/cpuinfo?

I was unable to reproduce this on a Raspberry Pi 3 Model B+ with:

pi@raspberrypi:~ $ cat /proc/cpuinfo
processor       : 0
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 38.40
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

processor       : 1
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 38.40
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

processor       : 2
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 38.40
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

processor       : 3
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 38.40
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 4

Hardware        : BCM2835
Revision        : a020d3
Serial          : 000000005c9c6a5d

[wblake0000]

I have the same problem. I have the RPI Model B Rev 1. Dump from cat /pro/cpuinfo
cat /proc/cpuinfo
processor : 0
model name : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 697.95
Features : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7

Hardware : BCM2835
Revision : 0002
Serial : 00000000d75050bd

FYI 18.06.1 did not have this issue. Going back to 18.06.1 worked successfully.
Update Spoke too soon. 18.06.1 did not seg fault on the dockerd but still had the containerd illegal instruction so containers don't appear to work

[agilob]

I believe the logs above are enough to diagnose the issue, but I'll add my logs too. Raspberry pi 1.

invoke-rc.d docker restart
Job for docker.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "restart" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: core-dump) since Mon 2018-11-12 19:46:18 UTC; 2s ago
     Docs: https://docs.docker.com
  Process: 1161 ExecStart=/usr/bin/dockerd -H unix:// (code=dumped, signal=SEGV)
 Main PID: 1161 (code=dumped, signal=SEGV)
      CPU: 438ms

Nov 12 19:46:18 rpi1 systemd[1]: docker.service: Main process exited, code=dumped, status=11/SEGV
Nov 12 19:46:18 rpi1 systemd[1]: Failed to start Docker Application Container Engine.
Nov 12 19:46:18 rpi1 systemd[1]: docker.service: Unit entered failed state.
Nov 12 19:46:18 rpi1 systemd[1]: docker.service: Failed with result 'core-dump'.
Nov 12 19:46:21 rpi1 systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Nov 12 19:46:21 rpi1 systemd[1]: Stopped Docker Application Container Engine.
Nov 12 19:46:21 rpi1 systemd[1]: Starting Docker Application Container Engine...
root@rpi1:/home/pi# systemctl start docker
Job for docker.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status docker.service" and "journalctl -xe" for details.
root@rpi1:/home/pi# journalctl -xe
Nov 12 19:46:31 rpi1 systemd[1]: containerd.service: Failed with result 'core-dump'.
Nov 12 19:46:47 rpi1 systemd[1]: docker.service: Start request repeated too quickly.
Nov 12 19:46:47 rpi1 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker.service has failed.
-- 
-- The result is failed.
Nov 12 19:46:47 rpi1 systemd[1]: docker.service: Failed with result 'core-dump'.
Nov 12 19:46:47 rpi1 systemd[1]: Starting containerd container runtime...
-- Subject: Unit containerd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit containerd.service has begun starting up.
Nov 12 19:46:47 rpi1 systemd[1]: Started containerd container runtime.
-- Subject: Unit containerd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit containerd.service has finished starting up.
-- 
-- The start-up result is done.
Nov 12 19:46:47 rpi1 systemd[1]: containerd.service: Main process exited, code=dumped, status=4/ILL
Nov 12 19:46:47 rpi1 systemd[1]: containerd.service: Unit entered failed state.
Nov 12 19:46:47 rpi1 systemd[1]: containerd.service: Failed with result 'core-dump'.


root@rpi1:/home/pi# /usr/bin/dockerd-ce 
Segmentation fault

[thaJeztah]

@agilob can you post the output of cat /proc/cpuinfo ?

[agilob]

pi@rpi1:~ $ cat /proc/cpuinfo
processor       : 0
model name      : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS        : 997.08
Features        : half thumb fastmult vfp edsp java tls 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb76
CPU revision    : 7

Hardware        : BCM2835
Revision        : 000f
Serial          : 00000000c06f1f2c

[sapkra]

I have the same problem with the Raspberry Pi Zero W - which has an older ARM CPU.

[agilob]

@sapkra rpi0w has almost the same CPU as 1B+. This works fine on my raspi0, but that's older version of docker: (.06 not .09)

pi@rpi0:~ $ sudo docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:30:52 2018
 OS/Arch:           linux/arm
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:26:37 2018
  OS/Arch:          linux/arm
  Experimental:     false
pi@rpi0:~ $ cat /proc/cpuinfo 
processor       : 0
model name      : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS        : 997.08
Features        : half thumb fastmult vfp edsp java tls 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb76
CPU revision    : 7

Hardware        : BCM2835
Revision        : 9000c1
Serial          : 000000000227ba1b

You can downgrade to a working version sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

[agilob]

I also confirm 18.09 works fine on raspberry pi 3:

pi@rpi3:~ $ sudo docker version
Client:
 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:57:21 2018
 OS/Arch:           linux/arm
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.0
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       4d60db4
  Built:            Wed Nov  7 00:17:57 2018
  OS/Arch:          linux/arm
  Experimental:     false
pi@rpi3:~ $ sudo docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
pi@rpi3:~ $ sudo systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2018-11-13 10:21:51 GMT; 46s ago
     Docs: https://docs.docker.com
 Main PID: 6337 (dockerd)
   Memory: 68.9M
      CPU: 2.960s
   CGroup: /system.slice/docker.service
           ├─ 6337 /usr/bin/dockerd -H unix://
           └─24195 docker-containerd-shim -namespace moby -workdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/b6e150046b81ddde1ba1a6eb2853f88e403d6eb147529e70173ebb9876899f4d -address /var/run/docker/containerd/docke

Nov 13 10:21:41 rpi3 dockerd[6337]: time="2018-11-13T10:21:41.177308277Z" level=warning msg="Your kernel does not support cgroup rt period"
Nov 13 10:21:41 rpi3 dockerd[6337]: time="2018-11-13T10:21:41.177440671Z" level=warning msg="Your kernel does not support cgroup rt runtime"
Nov 13 10:21:41 rpi3 dockerd[6337]: time="2018-11-13T10:21:41.178585765Z" level=warning msg="mountpoint for pids not found"
Nov 13 10:21:41 rpi3 dockerd[6337]: time="2018-11-13T10:21:41.180547777Z" level=info msg="Loading containers: start."
Nov 13 10:21:44 rpi3 dockerd[6337]: time="2018-11-13T10:21:44.399340311Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Nov 13 10:21:47 rpi3 dockerd[6337]: time="2018-11-13T10:21:47.528665834Z" level=info msg="Loading containers: done."
Nov 13 10:21:50 rpi3 dockerd[6337]: time="2018-11-13T10:21:50.998381326Z" level=info msg="Docker daemon" commit=4d60db4 graphdriver(s)=overlay2 version=18.09.0
Nov 13 10:21:51 rpi3 dockerd[6337]: time="2018-11-13T10:21:51.000858751Z" level=info msg="Daemon has completed initialization"
Nov 13 10:21:51 rpi3 dockerd[6337]: time="2018-11-13T10:21:51.338383593Z" level=info msg="API listen on /var/run/docker.sock"
Nov 13 10:21:51 rpi3 systemd[1]: Started Docker Application Container Engine.

[ReallyAwesomeShoes]

I have the same problem with the Raspberry Pi Zero W armv6l. Docker 18.09.0 service failed to run after installation, no matter what, failed !

[seemethere]

Yeah seems that the problem is isolated to armv6l although the build process for the arm bits hasn't changed at all.

Still trying to isolate the problem but don't currently have the hardware to test properly.

[ReallyAwesomeShoes]

Is there a way for us to help you to test it ? I have some spare Pi zero at home.

[DutchessNicole]

@seemethere
```pi@raspberrypi:~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 697.95
Features : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7

Hardware : BCM2835
Revision : 000d
Serial : 00000000857eb250
```

Sorry for the late reply. I've had surgery a few days ago and I'm not particularly lucid yet.
Please just let me know if you need anything else.

[cjdcordeiro]

I've the same problem on RPi Zero W.

@thaJeztah says https://docs.docker.com/install/linux/docker-ce/debian/#install-docker-ce-1 is doable for RPi, but on top there's a note saying you can't install from a repository for Raspbian...so that's a bit confusing. I've managed to install apt-get install docker-ce=18.06.1~ce~3-0~debian nevertheless (not raspbian), but still, I have the same problem. If I downgrade more onto 18.06.0 I'll then get a Illegal instruction.

So I'm not sure how you guys: 1st downgraded to an older raspbian version of docker; and 2nd, made it work cause for me it is still failing (with the debian version).

It is worth saying that it used to work for me in the past with 18.06...-raspbian

[agilob]

@seemethere I can import your ssh key from github and add this to my ssh-server raspi0 where you could try things if that helps?

[ReallyAwesomeShoes]

Here is the output for docker version command when I tried to install with the "curl -sSL https://get.docker.com | sh".

Client:
Version: 18.09.0
API version: 1.39
Go version: go1.10.4
Git commit: 4d60db4
Built: Wed Nov 7 00:57:21 2018
OS/Arch: linux/arm
Experimental: false
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/version: dial unix /var/run/docker.sock: connect: permission denied

[nicholasrobertm]

Thanks for looking into this! I've added all associating details on the other card here:
https://github.com/docker/for-linux/issues/490

If anything else is needed let me know and I'll pull it!

[nicholasrobertm]

Also to be clear for those having issues, to resolve this (on ARM 6 at least) I've confirmed running:
sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

Resolves the issue (It will downgrade versions)

[ReallyAwesomeShoes]

Not for me :-(

Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
The following additional packages will be installed:
  aufs-dkms aufs-tools cgroupfs-mount cpp-4.6 dkms gcc-4.6 git git-man liberror-perl libltdl7 linux-headers-3.6-trunk-common
  linux-headers-3.6-trunk-rpi linux-kbuild-3.6 linux-kbuild-4.9 pigz
Paquets suggérés :
  aufs-dev gcc-4.6-locales python3-apport menu libmudflap0-4.6-dev gcc-4.6-doc libgcc1-dbg libgomp1-dbg libquadmath-dbg libmudflap0-dbg
  libcloog-ppl1 | libcloog-ppl0 libppl-c4 libppl12 | libppl9 binutils-gold git-daemon-run | git-daemon-sysvinit git-doc git-el git-email
  git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn
Les NOUVEAUX paquets suivants seront installés :
  aufs-dkms aufs-tools cgroupfs-mount cpp-4.6 dkms docker-ce gcc-4.6 git git-man liberror-perl libltdl7 linux-headers-3.6-trunk-common
  linux-headers-3.6-trunk-rpi linux-kbuild-3.6 linux-kbuild-4.9 pigz
0 mis à jour, 16 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 47,9 Mo dans les archives.
Après cette opération, 216 Mo d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Réception de:1 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf liberror-perl all 0.17024-1 [26,9 kB]
Réception de:2 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf git-man all 1:2.11.0-3+deb9u4 [1 433 kB]
Réception de:9 https://download.docker.com/linux/raspbian stretch/stable armhf docker-ce armhf 18.06.1~ce~3-0~raspbian [28,3 MB]
Réception de:3 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf git armhf 1:2.11.0-3+deb9u4 [3 390 kB]                     
Réception de:4 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf pigz armhf 2.3.4-1 [50,0 kB]                               
Réception de:5 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf dkms all 2.3-2 [74,8 kB]                                   
Réception de:6 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf linux-kbuild-4.9 armhf 4.9.82-1+deb9u3+rpi1 [709 kB]       
Réception de:7 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf aufs-dkms armhf 4.9+20161219-1 [169 kB]                    
Réception de:8 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf aufs-tools armhf 1:4.1+20161219-1 [101 kB]                 
Réception de:10 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf cgroupfs-mount all 1.3 [5 716 B]                          
Réception de:11 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf cpp-4.6 armhf 4.6.4-5+rpi1 [4 145 kB]                     
Réception de:12 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf libltdl7 armhf 2.4.6-2 [386 kB]                           
Réception de:13 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf gcc-4.6 armhf 4.6.4-5+rpi1 [4 363 kB]                     
Réception de:14 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf linux-headers-3.6-trunk-common armhf 3.6.9-1~experimental.1+rpi7 [4 189 kB]
Réception de:15 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf linux-kbuild-3.6 armhf 3.6-1~experimental.1+rpi2+b2 [136 kB]
Réception de:16 http://mirrors.ircam.fr/pub/raspbian/raspbian stretch/main armhf linux-headers-3.6-trunk-rpi armhf 3.6.9-1~experimental.1+rpi7 [414 kB]
47,9 Mo réceptionnés en 2min 41s (297 ko/s)                                                                                                
Sélection du paquet liberror-perl précédemment désélectionné.
(Lecture de la base de données... 36343 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../00-liberror-perl_0.17024-1_all.deb ...
Dépaquetage de liberror-perl (0.17024-1) ...
Sélection du paquet git-man précédemment désélectionné.
Préparation du dépaquetage de .../01-git-man_1%3a2.11.0-3+deb9u4_all.deb ...
Dépaquetage de git-man (1:2.11.0-3+deb9u4) ...
Sélection du paquet git précédemment désélectionné.
Préparation du dépaquetage de .../02-git_1%3a2.11.0-3+deb9u4_armhf.deb ...
Dépaquetage de git (1:2.11.0-3+deb9u4) ...
Sélection du paquet pigz précédemment désélectionné.
Préparation du dépaquetage de .../03-pigz_2.3.4-1_armhf.deb ...
Dépaquetage de pigz (2.3.4-1) ...
Sélection du paquet dkms précédemment désélectionné.
Préparation du dépaquetage de .../04-dkms_2.3-2_all.deb ...
Dépaquetage de dkms (2.3-2) ...
Sélection du paquet linux-kbuild-4.9 précédemment désélectionné.
Préparation du dépaquetage de .../05-linux-kbuild-4.9_4.9.82-1+deb9u3+rpi1_armhf.deb ...
Dépaquetage de linux-kbuild-4.9 (4.9.82-1+deb9u3+rpi1) ...
Sélection du paquet aufs-dkms précédemment désélectionné.
Préparation du dépaquetage de .../06-aufs-dkms_4.9+20161219-1_armhf.deb ...
Dépaquetage de aufs-dkms (4.9+20161219-1) ...
Sélection du paquet aufs-tools précédemment désélectionné.
Préparation du dépaquetage de .../07-aufs-tools_1%3a4.1+20161219-1_armhf.deb ...
Dépaquetage de aufs-tools (1:4.1+20161219-1) ...
Sélection du paquet cgroupfs-mount précédemment désélectionné.
Préparation du dépaquetage de .../08-cgroupfs-mount_1.3_all.deb ...
Dépaquetage de cgroupfs-mount (1.3) ...
Sélection du paquet cpp-4.6 précédemment désélectionné.
Préparation du dépaquetage de .../09-cpp-4.6_4.6.4-5+rpi1_armhf.deb ...
Dépaquetage de cpp-4.6 (4.6.4-5+rpi1) ...
Sélection du paquet libltdl7:armhf précédemment désélectionné.
Préparation du dépaquetage de .../10-libltdl7_2.4.6-2_armhf.deb ...
Dépaquetage de libltdl7:armhf (2.4.6-2) ...
Sélection du paquet docker-ce précédemment désélectionné.
Préparation du dépaquetage de .../11-docker-ce_18.06.1~ce~3-0~raspbian_armhf.deb ...
Dépaquetage de docker-ce (18.06.1~ce~3-0~raspbian) ...
Sélection du paquet gcc-4.6 précédemment désélectionné.
Préparation du dépaquetage de .../12-gcc-4.6_4.6.4-5+rpi1_armhf.deb ...
Dépaquetage de gcc-4.6 (4.6.4-5+rpi1) ...
Sélection du paquet linux-headers-3.6-trunk-common précédemment désélectionné.
Préparation du dépaquetage de .../13-linux-headers-3.6-trunk-common_3.6.9-1~experimental.1+rpi7_armhf.deb ...
Dépaquetage de linux-headers-3.6-trunk-common (3.6.9-1~experimental.1+rpi7) ...
Sélection du paquet linux-kbuild-3.6 précédemment désélectionné.
Préparation du dépaquetage de .../14-linux-kbuild-3.6_3.6-1~experimental.1+rpi2+b2_armhf.deb ...
Dépaquetage de linux-kbuild-3.6 (3.6-1~experimental.1+rpi2+b2) ...
Sélection du paquet linux-headers-3.6-trunk-rpi précédemment désélectionné.
Préparation du dépaquetage de .../15-linux-headers-3.6-trunk-rpi_3.6.9-1~experimental.1+rpi7_armhf.deb ...
Dépaquetage de linux-headers-3.6-trunk-rpi (3.6.9-1~experimental.1+rpi7) ...
Paramétrage de aufs-tools (1:4.1+20161219-1) ...
Paramétrage de git-man (1:2.11.0-3+deb9u4) ...
Paramétrage de liberror-perl (0.17024-1) ...
Paramétrage de cpp-4.6 (4.6.4-5+rpi1) ...
Paramétrage de linux-headers-3.6-trunk-common (3.6.9-1~experimental.1+rpi7) ...
Paramétrage de cgroupfs-mount (1.3) ...
Paramétrage de dkms (2.3-2) ...
Paramétrage de linux-kbuild-4.9 (4.9.82-1+deb9u3+rpi1) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.24-11+deb9u3) ...
Traitement des actions différées (« triggers ») pour systemd (232-25+deb9u6) ...
Paramétrage de libltdl7:armhf (2.4.6-2) ...
Paramétrage de gcc-4.6 (4.6.4-5+rpi1) ...
Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ...
Paramétrage de linux-kbuild-3.6 (3.6-1~experimental.1+rpi2+b2) ...
Paramétrage de pigz (2.3.4-1) ...
Paramétrage de git (1:2.11.0-3+deb9u4) ...
Paramétrage de docker-ce (18.06.1~ce~3-0~raspbian) ...
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
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: activating (auto-restart) (Result: exit-code) since Sat 2018-11-17 17:16:54 CET; 172ms ago
     Docs: https://docs.docker.com
  Process: 10263 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
 Main PID: 10263 (code=exited, status=1/FAILURE)
      CPU: 1.641s

nov. 17 17:16:54 Raspi systemd[1]: docker.service: Unit entered failed state.
nov. 17 17:16:54 Raspi systemd[1]: docker.service: Failed with result 'exit-code'.
nov. 17 17:16:54 Raspi systemd[1]: docker.service: Service hold-off time over, scheduling restart.
nov. 17 17:16:54 Raspi systemd[1]: Stopped Docker Application Container Engine.
dpkg: erreur de traitement du paquet docker-ce (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Paramétrage de aufs-dkms (4.9+20161219-1) ...
Loading new aufs-4.9+20161219 DKMS files...
It is likely that 4.14.71+ belongs to a chroot's host
Building for 3.6-trunk-rpi, 4.14.79+ and 4.14.79-v7+
Building initial module for 3.6-trunk-rpi
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Skipped.
Module build for kernel 4.14.79+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel 4.14.79-v7+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Paramétrage de linux-headers-3.6-trunk-rpi (3.6.9-1~experimental.1+rpi7) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.6-trunk-rpi
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Traitement des actions différées (« triggers ») pour libc-bin (2.24-11+deb9u3) ...
Traitement des actions différées (« triggers ») pour systemd (232-25+deb9u6) ...
Des erreurs ont été rencontrées pendant l'exécution :
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

[nicholasrobertm]

Not for me :-(

Did you run the docker install script first before doing this? My steps were:
Install rasbian lite image
Enable ssh on the pi, and setup network config
Run docker install script here
Run sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

Otherwise are you on different hardware or something like that? Would need further details otherwise

[ReallyAwesomeShoes]

Hi nicholasrobertm,

thanks for your help ! Here is my hardware version of the pi :

processor : 0
model name : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 997.08
Features : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7

Hardware : BCM2835
Revision : 9000c1
Serial : 000000000d2025f7

In fact, you're right, you just need to do what you described first, no update no upgrade and all works fine.

Thanks, you save my day !

[seemethere]

So I got a raspberry pi 0 setup and have found that most of our static binary bits are coming down with a seg fault / illegal instruction as well:

These are from: https://download.docker.com/linux/static/stable/armhf/docker-18.09.0.tgz

pi@raspberrypi:~ $ for binary in ./armhf/*; do echo $binary; $binary 2>/dev/null; done
./armhf/containerd
Segmentation fault
./armhf/containerd-shim
./armhf/ctr
Segmentation fault
./armhf/docker
./armhf/dockerd
Segmentation fault
./armhf/docker-init
Illegal instruction
./armhf/docker-proxy
./armhf/runc
Illegal instruction

This leads me to believe it might be a golang issue that's actually causing this, some output from gdb on some of our binaries:

runc

./armhf/runc
Reading symbols from ./armhf/runc...done.
Starting program: /home/pi/armhf/runc
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x0005f04a in runtime.typelinksinit ()
#0  0x0005f04a in runtime.typelinksinit ()
#1  0x0001052e in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

dockerd

./armhf/dockerd
Reading symbols from ./armhf/dockerd...done.
Starting program: /home/pi/armhf/dockerd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x0005db14 in runtime.slicerunetostring ()
#0  0x0005db14 in runtime.slicerunetostring ()
#1  0x0001052a in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

ctr

./armhf/ctr
Reading symbols from ./armhf/ctr...(no debugging symbols found)...done.
Starting program: /home/pi/armhf/ctr

Program received signal SIGSEGV, Segmentation fault.
0x0005f3b8 in ?? ()
#0  0x0005f3b8 in ?? ()
#1  0x0001037e in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

containerd

./armhf/containerd
Reading symbols from ./armhf/containerd...(no debugging symbols found)...done.
Starting program: /home/pi/armhf/containerd

Program received signal SIGSEGV, Segmentation fault.
0x0005ea66 in ?? ()
#0  0x0005ea66 in ?? ()
#1  0x0001037e in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

docker-init

./armhf/docker-init
Reading symbols from ./armhf/docker-init...(no debugging symbols found)...done.
Starting program: /home/pi/armhf/docker-init

Program received signal SIGILL, Illegal instruction.
0x00010a62 in ?? ()
#0  0x00010a62 in ?? ()
#1  0x00062b52 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

[DutchessNicole]

Also to be clear for those having issues, to resolve this (on ARM 6 at least) I've confirmed running:
sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

Resolves the issue (It will downgrade versions)

This did resolve the issue for me, at least temporarily. Thank you for this workaround!

[gbrault]

@seemethere do you have any idea if this can / will be corrected? Or does it mean docker compatibility with armv6 will stop? Of course I have applied @nicholasrobertm and it works great! Thx nicholas.

[StefanSchoof]

Or can you at least remove this broken armv6 build from the package repository. So that a apt-get install results into the working 18.06.1 version. Otherwise more people will run into this problem.

[gbrault]

I have also another small issue: docker doesn't start at boot when enabled with systemd (using raspbian on raspberry zero w November release).
I found a turnarround solution adding in /lib/systemd/system/docker.service getty.target in After

After=network-online.target docker.socket firewalld.service getty.target

I open the docker IP with
ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375 -H fd://

adding the tcp binding...

One issue docker find is that cgroups seems not managed and the OOM monitoring fails see attached
docker.txt

[StefanSchoof]

To get my apt-get upgrade working again, I created a apt pinning file under /etc/apt/preferences.d/docker-ce :

Package: docker-ce
Pin: version 18.06.*
Pin-Priority: 1000

Edit 20190213: Allow update to 18.06.2 to get fix for CVE-2019-5736

[FlorianHeigl]

+1 for removing the package from repo. It's broken, why is it there, in stable.

[simonerom]

+1 for removing the package from repo. It's broken, why is it there, in stable.

I confirm this is still the standard (broken) package that gets installed on raspberry pi (both with apt-get and with script method)

[raymop]

+1 This fix worked for me. please remove package from repo.

[marcostrullato]

Same issue here. Please let me know once fixed.
Tnks

[nickcj931]

Same issue for me using Raspberry Pi Zero, the fix worked

[wlisac]

Also to be clear for those having issues, to resolve this (on ARM 6 at least) I've confirmed running:
sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian
Resolves the issue (It will downgrade versions)

This did resolve the issue for me, at least temporarily. Thank you for this workaround!

Experienced this same issue today. The workaround fixed it for now.

[rmoriz]

I really wish Docker would fix the issue, probably it's some Golang compilation flag (GOARM=6). Hypriot had to downgrade Docker as well https://github.com/hypriot/image-builder-rpi/commit/c5beaa96fd6674b179cfc1fa477d10c200ef25ed

I tried to understand the build and release workflow of docker-ce. It looks like there is no cross-compilation (anymore) and the whole packaging has to be done on the destination architecture? I guess this happens on modern RPI3 using Raspbian Stretch which automatically selects the kernel/architecture (the same image is capable of booting armv6l on old RPI and armv7l on newer RPIs)

[timdonovanuk]

Still broken when using get.docker.com/get-docker.sh/apt-get. My first time installing docker and none of the install instructions for Pi worked. Very frustrating 2 hours -_-

"sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian" this works!

[yuusou]

May I ask when can we expected a fixed docker-ce for the old RPi?

[zipy124]

I downgraded my docker-ce, but docker-ce-cli is incompatible with this version, from what repo can i install an older version of that too?

[thaJeztah]

older versions of docker-ce (before 18.09) did not yet have a separate docker-ce-cli package, so you can uninstall the docker-ce-cli (and containerd.io) package before downgrading

[zipy124]

older versions of docker-ce (before 18.09) did not yet have a separate docker-ce-cli package, so you can uninstall the docker-ce-cli (and containerd.io) package before downgrading

Ok, thank you very much! I hope this issue is fixed at some point.

[rmoriz]

@thaJeztah can you share with us how the raspbian packages were built? So that we can built our own packages and try to debug the issue?

[thaJeztah]

Packaging scripts are in the https://github.com/docker/docker-ce-packaging repository

[rmoriz]

@thaJeztah and for the containerd.io dependency package?

Why are there https://github.com/docker/docker-ce-packaging and https://github.com/docker/docker-ce/tree/master/components/packaging?

I think the breaking commit was https://github.com/docker/docker-ce/commit/d9d726eb2b2126ce75932835317e8ff48a075ac3#diff-65f726e7a1a1fd3b9b9b03b6e3dc8409 due to the removal of arch-specific Dockerfiles (and with that the GOARM=6 env variable to build arm binaries for older cpu types). However just adding the ENV GOARM 6 to the current Dockerfile does not help, because of the other new dependencies throughout the project (and containerd)

[nnarain]

Experienced this issue today. Workaround got me into a non-coredumping state. However docker run hello-world has no output.

Any place I can check the logs for that container's run?

[leighghunt]

Experienced this issue today. Workaround got me into a non-coredumping state. However docker run hello-world has no output.

Any place I can check the logs for that container's run?

Hey @nnarain, I get exactly the same symptoms after pinning to 18.06.1 on a vanilla Raspbian image on a Zero W. Did you end up resolving it?

My entire session from first log on:

Linux raspberrypi 4.14.79+ #1159 Sun Nov 4 17:28:08 GMT 2018 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

SSH is enabled and the default password for the 'pi' user has not been changed.
This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.

pi@raspberrypi:~ $ echo -e "Package: docker-ce\nPin: version 18.06.1*\nPin-Priority: 1000" | sudo tee /etc/apt/preferences
Package: docker-ce
Pin: version 18.06.1*
Pin-Priority: 1000
pi@raspberrypi:~ $ curl -fsSL get.docker.com -o get-docker.sh && sh get-docker.sh
# Executing docker install script, commit: 26dda3d
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c 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 stretch edge" > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
+ sudo -E sh -c docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:30:52 2018
 OS/Arch:           linux/arm
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:26:37 2018
  OS/Arch:          linux/arm
  Experimental:     false
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 pi

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/security/#docker-daemon-attack-surface
         for more information.
pi@raspberrypi:~ $ sudo usermod -aG docker pi
pi@raspberrypi:~ $ exit



logout
Connection to 10.1.10.53 closed.
✘-126 ~ 

16:06 $ ssh [email protected]
[email protected]'s password: 
Linux raspberrypi 4.14.79+ #1159 Sun Nov 4 17:28:08 GMT 2018 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Feb 13 02:59:05 2019 from 10.1.10.10

SSH is enabled and the default password for the 'pi' user has not been changed.
This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.

pi@raspberrypi:~ $ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
c1eda109e4da: Pull complete 
Digest: sha256:2557e3c07ed1e38f26e389462d03ed943586f744621577a99efb77324b0fe535
Status: Downloaded newer image for hello-world:latest
pi@raspberrypi:~ $

pi@raspberrypi:~ $ sudo service docker status
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-02-13 03:05:50 GMT; 1min 50s ago
     Docs: https://docs.docker.com
 Main PID: 2131 (dockerd)
   CGroup: /system.slice/docker.service
           ├─2131 /usr/bin/dockerd -H fd://
           └─2137 docker-containerd --config /var/run/docker/containerd/containerd.toml

Feb 13 03:05:44 raspberrypi dockerd[2131]: time="2019-02-13T03:05:44.363766207Z" level=info msg="Loading containers: done."
Feb 13 03:05:47 raspberrypi dockerd[2131]: time="2019-02-13T03:05:47.872627610Z" level=info msg="Docker daemon" commit=e68fc7a graphdriver(s)=overlay2 version=18.06.1-ce
Feb 13 03:05:47 raspberrypi dockerd[2131]: time="2019-02-13T03:05:47.879247525Z" level=info msg="Daemon has completed initialization"
Feb 13 03:05:50 raspberrypi dockerd[2131]: time="2019-02-13T03:05:50.091012045Z" level=warning msg="Could not register builder git source: failed to find git binary: exec: \"git\": executable file not found in $PATH"
Feb 13 03:05:50 raspberrypi systemd[1]: Started Docker Application Container Engine.
Feb 13 03:05:50 raspberrypi dockerd[2131]: time="2019-02-13T03:05:50.322462079Z" level=info msg="API listen on /var/run/docker.sock"
Feb 13 03:07:08 raspberrypi dockerd[2131]: time="2019-02-13T03:07:08Z" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/38424af8336944d9c53df3d92a5d5f2346c6c64cea1292c11dddd2b2b101e164/shim.sock" debug=false pid=2415
Feb 13 03:07:10 raspberrypi dockerd[2131]: time="2019-02-13T03:07:10Z" level=warning msg="OOM monitoring failed" error="cgroups: memory cgroup not supported on this system"
Feb 13 03:07:13 raspberrypi dockerd[2131]: time="2019-02-13T03:07:13Z" level=info msg="shim reaped" id=38424af8336944d9c53df3d92a5d5f2346c6c64cea1292c11dddd2b2b101e164
Feb 13 03:07:13 raspberrypi dockerd[2131]: time="2019-02-13T03:07:13.389047785Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"




pi@raspberrypi:~ $ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                       PORTS               NAMES
1021e90b4c83        hello-world         "/hello"            4 minutes ago       Exited (139) 4 minutes ago                       trusting_pare
38424af83369        hello-world         "/hello"            10 minutes ago      Exited (139) 9 minutes ago                       compassionate_brattain
pi@raspberrypi:~ $ 

UPDATE: However, other images appear to work:

pi@raspberrypi:~ $ docker run -it alpine /bin/sh
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
05276f4299f2: Pull complete 
5657e63df536: Pull complete 
Digest: sha256:b3dbf31b77fd99d9c08f780ce6f5282aba076d70a513a8be859d8d3a4d0c92b8
Status: Downloaded newer image for alpine:latest
/ # ls
bin    dev    etc    home   lib    media  mnt    opt    proc   root   run    sbin   srv    sys    tmp    usr    var
/ # exit
pi@raspberrypi:~ $ 

[StefanSchoof]

With https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736 there is now no secure version for armv6

[rmoriz]

There is a „real“ open source version of docker 18.09 including all dependencies maintained at https://salsa.debian.org/docker-team which is used to built packages for Debian unstable (Sid). Sadly there is no Raspbian unstable and the armhf packages from Debian do not work on RP0 (segmentation fault). However it has the full sources and packaging setup so maybe it‘s just setting the right GOARM setting to fix it...

See also https://salsa.debian.org/docker-team/docker/blob/master/debian/README.source

[thaJeztah]

With https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736 there is now no secure version for armv6

@StefanSchoof does the 18.06.2-ce package work? (updated version of 18.06 with the fix for that CVE); https://download.docker.com/linux/raspbian/dists/stretch/pool/stable/armhf/

[StefanSchoof]

@thaJeztah yes it works. Thanks. So I was wrong and there is a secure version. I updated my /etc/apt/preferences.d/docker-ce to:

Package: docker-ce
Pin: version 18.06.*
Pin-Priority: 1000

to get the version.

[StefanScherer]

Can confirm, 18.06.2 works fine on Raspberry Pi Zero.
@nnarain @leighghunt running hello-world shows nothing, probably because the linux/arm/v7 image is pulled. Try docker run arm32v5/hello-world this works for me.

You can check the manifest list with docker run --rm mplatform/mquery hello-world even from your RPi.

$ docker run --rm mplatform/mquery hello-world
Unable to find image 'mplatform/mquery:latest' locally
latest: Pulling from mplatform/mquery
db6020507de3: Pull complete 
5107afd39b7f: Pull complete 
Digest: sha256:e15189e3d6fbcee8a6ad2ef04c1ec80420ab0fdcf0d70408c0e914af80dfb107
Status: Downloaded newer image for mplatform/mquery:latest
Image: hello-world
 * Manifest List: Yes
 * Supported platforms:
   - linux/amd64
   - linux/arm/v5
   - linux/arm/v7
   - linux/arm64
   - linux/386
   - linux/ppc64le
   - linux/s390x
   - windows/amd64:10.0.14393.2551
   - windows/amd64:10.0.16299.846
   - windows/amd64:10.0.17134.469
   - windows/amd64:10.0.17763.194

[leighghunt]

@stefanberger, bingo! Thanks :-)

pi@raspberrypi:~$ docker run hello-world
139 pi@raspberrypi:~$ docker run arm32v5/hello-world
Unable to find image 'arm32v5/hello-world:latest' locally
latest: Pulling from arm32v5/hello-world
590e13f69e4a: Pull complete
Digest: sha256:8a6a26a494c03e91381161abe924a39a2ff72de13189edcc2ed1695e6be12a5f
Status: Downloaded newer image for arm32v5/hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (arm32v5)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

pi@raspberrypi:~$

[AWDDude]

Just confirmed that latest version "18.09.03-0 raspbian-stretch armhf" still does not work on Raspberry Pi Zero.

[mahmoudgamal]

This did resolve the issue for me, at least temporarily. Thank you for this workaround!

Thank you for this workaround!

[HostileRobot]

@thaJeztah yes it works. Thanks. So I was wrong and there is a secure version. I updated my /etc/apt/preferences.d/docker-ce to:

Package: docker-ce
Pin: version 18.06.*
Pin-Priority: 1000

to get the version.

This fix did not work for me; docker.service isn't starting up on my Raspberry Pi Zero:

docker.service: Main process exited, code=dumped, status=11/SEGV
Failed to start Docker Application Container Engine.
docker.service: Unit entered failed state.
docker.service: Failed with result 'core-dump'.

Any other ideas?

[yuusou]

You still need to downgrade your docker-ce package.

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

[mahmoudgamal]

@thaJeztah yes it works. Thanks. So I was wrong and there is a secure version. I updated my /etc/apt/preferences.d/docker-ce to:

Package: docker-ce
Pin: version 18.06.*
Pin-Priority: 1000

to get the version.

This fix did not work for me; docker.service isn't starting up on my Raspberry Pi Zero:

docker.service: Main process exited, code=dumped, status=11/SEGV
Failed to start Docker Application Container Engine.
docker.service: Unit entered failed state.
docker.service: Failed with result 'core-dump'.

Any other ideas?
@HostileRobot
Try this
sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

[HostileRobot]

I just noticed that I didn't add https://download.docker.com/linux/raspbian in my sources, my bad. Pinning version 18.06.* works now.
Thanks.

[moan18]

@sapkra rpi0w has almost the same CPU as 1B+. This works fine on my raspi0, but that's older version of docker: (.06 not .09)

pi@rpi0:~ $ sudo docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:30:52 2018
 OS/Arch:           linux/arm
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:26:37 2018
  OS/Arch:          linux/arm
  Experimental:     false
pi@rpi0:~ $ cat /proc/cpuinfo 
processor       : 0
model name      : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS        : 997.08
Features        : half thumb fastmult vfp edsp java tls 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb76
CPU revision    : 7

Hardware        : BCM2835
Revision        : 9000c1
Serial          : 000000000227ba1b

You can downgrade to a working version sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

I uninstall the latest version >>> "sudo apt-get purge docker-ce" and "sudo rm -rf /var/lib/docker" then...

And install the version 18.06 >>> "sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian"

And.. Work!!! Thanks @agilob

[SuhanKoh]

@moan18 18.06.1~ce~3-0~raspbian for docker-ce was not found?

Update: Nevermind, I was able to install it via

echo "deb [arch=armhf] https://download.docker.com/linux/raspbian $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list sudo apt update

[thaJeztah]

To all here; please do not install 18.06.1, as it does not have the patch for the runc CVE that allows container escapes; install 18.06.2 instead

[fcrisciani]

for who has already the right repo in sources.list: sudo apt-get install docker-ce=18.06.2~ce~3-0~raspbian

[bobburgers7]

As an FYI, 18.06.3 was released 2/20/19. I installed it on my Pi Zero W and have been running it without issues

[ankurshah7]

I read whole thread. I purged docker-ce and downgraded to 18.06.3~ce~3-0~raspbian but I still have no success.

/proc/cpuinfo shows ARMv7 Processor rev 4 (v7l) ( Pi 3 B )

pi@RaspberryPi:~ $ docker version
Client:
Version: 18.06.3-ce
API version: 1.38
Go version: go1.10.3
Git commit: d7080c1
Built: Wed Feb 20 02:42:54 2019
OS/Arch: linux/arm
Experimental: false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

@seemethere - you have run it successfully on Pi 3B - can you suggest what should I do next ?

[StefanScherer]

@ankurshah7 it‘s hard to investigate what might be the problem wuth your installation. You could download the latest HypriotOS
https://blog.hypriot.com/downloads/ which has Docker 18.06.3 preinstalled.

[heliocosta]

I gave up, I had tried 100 different options to install and nothing on rpi0w

`sudo dpkg -i docker-ce_18.06.2~ce~3-0~debian_armhf.deb
(Reading database ... 91166 files and directories currently installed.)
Preparing to unpack docker-ce_18.06.2~ce~3-0~debian_armhf.deb ...
Unpacking docker-ce (18.06.2~ce~3-0~debian) over (18.06.2~ce~3-0~debian) ...
Setting up docker-ce (18.06.2~ce~3-0~debian) ...
Job for docker.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status docker.service" and "journalctl -xe" for details.
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: activating (start) since Tue 2019-02-26 01:53:04 GMT; 1s ago
Docs: https://docs.docker.com
Main PID: 1735 (dockerd)
CPU: 230ms
CGroup: /system.slice/docker.service
└─1735 /usr/bin/dockerd -H fd://

Feb 26 01:53:04 wine-server systemd[1]: Starting Docker Application Container Engine...
dpkg: error processing package docker-ce (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (232-25+deb9u9) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
docker-ce`

[yuusou]

This is all you need to get it working

sudo apt-get purge docker-ce
sudo apt-get install docker-ce=18.06.3~ce~3-0~raspbian
sudo systemctl enable docker && sudo systemctl start docker

From here you should be able to run the docker command under sudo and if your user is part of the docker group then you don't need sudo.

[heliocosta]

@yuusou the first line worked, but the second doesn't:

pi@wine-server:~ $ sudo apt-get purge docker-ce
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  aufs-dkms aufs-tools cgroupfs-mount dkms linux-headers-3.6-trunk-common linux-headers-3.6-trunk-rpi linux-kbuild-3.6 linux-kbuild-4.9 pigz
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  docker-ce*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 137 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 91346 files and directories currently installed.)
Removing docker-ce (18.06.2~ce~3-0~debian) ...
Processing triggers for man-db (2.7.6.1-2) ...
(Reading database ... 91131 files and directories currently installed.)
Purging configuration files for docker-ce (18.06.2~ce~3-0~debian) ...
Processing triggers for systemd (232-25+deb9u9) ...
pi@wine-server:~ $ sudo apt-get install docker-ce=18.06.3~ce~3-0~raspbian
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package docker-ce

[jcardy-thalmic]

@heliocosta

I did the following to get my rpi0 working;

To clean up my system

sudo apt-get purge docker-ce
sudo apt autoremove
sudo rm -rf /var/lib/docker

Then I installed using the docker script (since it looks like in your configuration you're missing adding the docker repo to apt). Most of the people on here have probably ran this script at one point or another.

curl -fsSL https://get.docker.com -o get-docker.sh
chmod u+x get-docker.sh
VERSION=18.06.3~ce~3-0~raspbian ./get-docker.sh

[ankurshah7]

I read whole thread. I purged docker-ce and downgraded to 18.06.3ce3-0~raspbian but I still have no success.

I finally got "5:18.09.0~3-0~raspbian-stretch" version running on "rpi3-ARMv7 Processor rev 4 (v7l)"

I had to do some cleanup and then attempt reinstall

*sudo rm -rf /etc/docker /etc/systemd/system/docker**

curl -fsSL https://get.docker.com -o get-docker.sh
chmod u+x get-docker.sh
./get-docker.sh

[reloxx13]

check if ur docker.socket exists in /lib/systemd/system/docker.socket

missing docker.socket is not the segmentation error.

get the socket with this:
sudo curl https://raw.githubusercontent.com/docker/docker-ce-packaging/master/systemd/docker.socket -o /lib/systemd/system/docker.socket

https://github.com/docker/for-linux/issues/476#issuecomment-437423363

[mockturtl]

re: jcardy-thalmic

VERSION=18.06.3\~ce\~3-0~raspbian ./get-docker.sh

This fails now.

$ VERSION=18.06.3~ce~3-0~raspbian ./get-docker.sh
...
INFO: Searching repository for VERSION '18.06.3~ce~3-0~raspbian'
INFO: apt-cache madison 'docker-ce' | grep '18.06.3~ce~3.*0~raspbian.*-0~raspbian' | head -1 | cut -d' ' -f 4  
# notice VERSION was mangled, grep pattern includes '~raspbian' twice
ERROR: '18.06.3~ce~3-0~raspbian' not found amongst apt-cache madison results
# wrong!

$ apt-cache madison docker-ce |grep '18.06.3~ce~3-0~raspbian'
# docker-ce | 18.06.3~ce~3-0~raspbian | https://download.docker.com/linux/raspbian stretch/stable armhf Packages

The problem is L392 of get-docker.sh:

pkg_pattern="$(echo "$VERSION" | sed "s/-ce-/~ce~.*/g" | sed "s/-/.*/g").*-0~$lsb_dist"
# replace with:  pkg_pattern="$VERSION"

[nicph]

@mockturtl in fact, VERSION=18.06.3 ./get-docker.sh works.

[jmb12686]

I am trying to revive my OG Raspberry Pi Model B+, and was unsuccessful at installing docker via the "get.docker.com" method (curl -sSL https://get.docker.com | sh). Afterwards, I ran the apt pkg manager installation with older version as many have posted before. This proved successful for me:

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

[luisRubiera]

I keep having problems with the Raspberry PI Zero W :

sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian
...
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.6-trunk-rpi
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.

uname -a
Linux raspberrypi 4.14.98+ #1200 Tue Feb 12 20:11:02 GMT 2019 armv6l GNU/Linux

for those wondering, Docker works correctly on Pi B+ and A+

[Diaoul]

sudo apt-get install 'docker-ce=18.06.*' will pick whatever is the latest from 18.06.

[diveyez]

The reason why we need it working on Pi0w is because of the classroom and pocket sized footprint for educational and economic viability. Ignoring the SBC's will lead to abandonment.

I had this working, for about 5 hours, then it dropped and just stopped attaching containers to the daemon. No idea why it does that.

[StefanScherer]

The segfaults are raised by containerd which is not compiled for ARMv6. For the HypriotOS we managed to compile and package it to be compatible for ARMv6 and can be found here https://packagecloud.io/Hypriot/rpi/packages/raspbian/stretch/containerd.io_1.2.6-1_armhf.deb
After installing that package and then Docker CE 19.03.0 beta should work on Pi Zero.

It will take a while until we got this changed package upstream.

[tanus10]

On Raspberry Pi 1B2
apt-get install docker-ce (installs 5:18.09.0~3-0~raspbian-stretch )
dpkg -i containerd.io_1.2.6-1_armhf.deb (downloaded. installs ok.)

Docker CE 19.03.0 does not work with containerd.io (1.2.6-1)

 # docker version
Client:
 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:57:21 2018
 OS/Arch:           linux/arm
 Experimental:      false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

I cannot get 'systemctl start docker.service' to work.
I thought installing containerd.io_1.2.6-1_armhf.deb would make Docker 18.09.0 work.
Purging Docker 18.09.0 and installing 18.06.3-ce works well.

BTW, popular practice of naming arm32/v7, arm32/v5, and arm32/v6 all as arm or armhf has to stop. So many docker packages labeled as 'arm' do not work on arm32/v5 or arm32/v6

[jonlorusso]

I don't know if this is related, or a separate issue, or just something I am doing wrong, but on a Pi Zero (armv6l) with docker-ce=18.06.1~ce~3-0~raspbian, I can run hypriot/armhf-hello-world (I could not run hello-world):

Hello from Docker.
This message shows that your installation appears to be working correctly.

However, if I try to build a fairly simple container:

FROM alpine

RUN mkdir /test

CMD echo "hello world"

It fails with a segfault:

pi@raspberrypi:~/test $ docker build .
Sending build context to Docker daemon  2.048kB
Step 1/3 : FROM alpine
latest: Pulling from library/alpine
856f4240f8db: Already exists
Digest: sha256:769fddc7cc2f0a1c35abb2f91432e8beecf83916c421420e6a6da9f8975464b6
Status: Downloaded newer image for alpine:latest
 ---> ea2ccc7da15e
Step 2/3 : RUN mkdir /test
 ---> Running in f36ae4e91210
The command '/bin/sh -c mkdir /test' returned a non-zero code: 139

[tanus10]

I don't know if this is related, or a separate issue, or just something I am doing wrong, but on a Pi Zero (armv6l) with docker-ce=18.06.1~ce~3-0~raspbian, I can run hypriot/armhf-hello-world (I could not run hello-world):

Hello from Docker.
This message shows that your installation appears to be working correctly.

However, if I try to build a fairly simple container:

FROM alpine

RUN mkdir /test

CMD echo "hello world"

It fails with a segfault:

pi@raspberrypi:~/test $ docker build .
Sending build context to Docker daemon  2.048kB
Step 1/3 : FROM alpine
latest: Pulling from library/alpine
856f4240f8db: Already exists
Digest: sha256:769fddc7cc2f0a1c35abb2f91432e8beecf83916c421420e6a6da9f8975464b6
Status: Downloaded newer image for alpine:latest
 ---> ea2ccc7da15e
Step 2/3 : RUN mkdir /test
 ---> Running in f36ae4e91210
The command '/bin/sh -c mkdir /test' returned a non-zero code: 139

Alpine image you used is not arm32v6 compatible. If it is labeled as arm then, it probably means arm32v7 image.

Not all 'arm32' or 'arm' images are arm32v6 compatible. Actually, most are not compatible. You might try images labeled as raspberry pi compatible. No guarantee though.

For Alpine, It seems there is an official Alpine image for arm32v6.
Try,
https://hub.docker.com/r/arm32v6/alpine/

I am having really hard time finding arm32v6 compatible images, trial and error seems the only way.

There isn't many arm32v6 images as arm32v7 images on the Hub. Unfortunately many arm32v6 images are not tested, making problem even worse. Not to mention many commonly used/included Docker image building helper tools are only available as arm32v7 compatible, so Developers are unable to provide arm32v6 images, not because the main program couldn't be compiled against arm32v6, but the building tools such as script engines, decompress executable, etc. are not available in arm32v6 compatible form.

I just installed Hypriot's Docker SD image on three Rpi 1's (armv6l) and having tremendous difficulty finding arm32v6 compatible images. Didn't see it coming.

[marcbihlmaier]

older than version 19.x is not available for Debian Buster, so what is the solution here?

root@raspberrypi:/home/pi# apt-cache madison 'docker-ce'
 docker-ce | 5:19.03.2~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages
 docker-ce | 5:19.03.1~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages

[tanus10]

https://blog.hypriot.com/downloads/
https://github.com/hypriot/image-builder-rpi/releases

I haven't tried it myself, but at least 19.03.1 (built for ARMv6) seems to work.
Not sure Hypriot used their own build/repo or official one. Oh, scratch that.
The document says "Docker Engine 19.03.1 (officially build by Docker)"

[mskwon]

older than version 19.x is not available for Debian Buster, so what is the solution here?

root@raspberrypi:/home/pi# apt-cache madison 'docker-ce'
 docker-ce | 5:19.03.2~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages
 docker-ce | 5:19.03.1~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages

It seems like there is still an issue with the containerd.io version. Try installing (or upgrading Docker) normally then run these commands to replace containerd.io with the ARMv6 compiled version put out by Hypriot.

wget -O /tmp/containerd.io_1.2.6-1_armhf.deb —content-disposition https://packagecloud.io/Hypriot/rpi/packages/raspbian/stretch/containerd.io_1.2.6-1_armhf.deb/download.deb

sudo apt install /tmp/containerd.io_1.2.6-1_armhf.deb

Docker CE 19.03.2 is working fine on my Raspberry Pi 1B with Raspbian Buster using this version of containerd.io.

Does anyone have any idea when packaging for containerd.io is going to be fixed in the Docker repo? Is this something I could help with?

[mentalburden]

older than version 19.x is not available for Debian Buster, so what is the solution here?

root@raspberrypi:/home/pi# apt-cache madison 'docker-ce'
 docker-ce | 5:19.03.2~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages
 docker-ce | 5:19.03.1~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages

It seems like there is still an issue with the containerd.io version. Try installing (or upgrading Docker) normally then run these commands to replace containerd.io with the ARMv6 compiled version put out by Hypriot.

wget -O /tmp/containerd.io_1.2.6-1_armhf.deb —content-disposition https://packagecloud.io/Hypriot/rpi/packages/raspbian/stretch/containerd.io_1.2.6-1_armhf.deb/download.deb

sudo apt install /tmp/containerd.io_1.2.6-1_armhf.deb

Docker CE 19.03.2 is working fine on my Raspberry Pi 1B with Raspbian Buster using this version of containerd.io.

Does anyone have any idea when packaging for containerd.io is going to be fixed in the Docker repo? Is this something I could help with?

This is what worked for my raspi zeros running buster. Thanks so much

[Caroga]

older than version 19.x is not available for Debian Buster, so what is the solution here?

root@raspberrypi:/home/pi# apt-cache madison 'docker-ce'
 docker-ce | 5:19.03.2~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages
 docker-ce | 5:19.03.1~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages

It seems like there is still an issue with the containerd.io version. Try installing (or upgrading Docker) normally then run these commands to replace containerd.io with the ARMv6 compiled version put out by Hypriot.
wget -O /tmp/containerd.io_1.2.6-1_armhf.deb —content-disposition https://packagecloud.io/Hypriot/rpi/packages/raspbian/stretch/containerd.io_1.2.6-1_armhf.deb/download.deb
sudo apt install /tmp/containerd.io_1.2.6-1_armhf.deb
Docker CE 19.03.2 is working fine on my Raspberry Pi 1B with Raspbian Buster using this version of containerd.io.
Does anyone have any idea when packaging for containerd.io is going to be fixed in the Docker repo? Is this something I could help with?

This is what worked for my raspi zeros running buster. Thanks so much

@mentalburden starting with a new installation of a pi zero, how would you say the steps would be to get it to work?

To elaborate: installing docker first, letting dpkg error out, replaced containerd.io with the patched version and run dpkg reconfigure or something else?

[Caroga]

older than version 19.x is not available for Debian Buster, so what is the solution here?

root@raspberrypi:/home/pi# apt-cache madison 'docker-ce'
 docker-ce | 5:19.03.2~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages
 docker-ce | 5:19.03.1~3-0~raspbian-buster | https://download.docker.com/linux/raspbian buster/stable armhf Packages

It seems like there is still an issue with the containerd.io version. Try installing (or upgrading Docker) normally then run these commands to replace containerd.io with the ARMv6 compiled version put out by Hypriot.
wget -O /tmp/containerd.io_1.2.6-1_armhf.deb —content-disposition https://packagecloud.io/Hypriot/rpi/packages/raspbian/stretch/containerd.io_1.2.6-1_armhf.deb/download.deb
sudo apt install /tmp/containerd.io_1.2.6-1_armhf.deb
Docker CE 19.03.2 is working fine on my Raspberry Pi 1B with Raspbian Buster using this version of containerd.io.
Does anyone have any idea when packaging for containerd.io is going to be fixed in the Docker repo? Is this something I could help with?

This is what worked for my raspi zeros running buster. Thanks so much

@mentalburden starting with a new installation of a pi zero, how would you say the steps would be to get it to work?

To elaborate: installing docker first, letting dpkg error out, replaced containerd.io with the patched version and run dpkg reconfigure or something else?

I found that installing docker, and running dpkg -i /tmp/containerd.io_1.2.6-1_armhf.deb instead of sudo apt install /tmp/containerd.io_1.2.6-1_armhf.deb worked better for me.
Ow, and a reboot ofcourse.
Working state on a freshly installed rpi zero.

[seemethere]

Hey guys!

Just released new containerd.io package version 1.2.10-2 to the https://download.docker.com repositories, please let me know if that resolves all issues related to this segmentation fault, I do not currently have a armv6 machine to test on.

Sorry for the late update on this, hopefully this issue is now resolved

[yuusou]

Magic stuff @seemethere ! That's finally fixed it! Thank you!

[StefanScherer]

I flashed the latest Raspbian Lite and ran curl https://get.docker.com | sh on a Raspberry Pi Zero and ran some containers. Everything works. Excellent, thanks @seemethere !!

[leifnel]

I deleted docker and tried reinstalling.

I removed the -qq and >/dev/null from the get.docker.com script to see what happened.

The following additional packages will be installed:
  docker-ce-cli
Recommended packages:
  aufs-tools cgroupfs-mount | cgroup-lite pigz
The following NEW packages will be installed:
  docker-ce docker-ce-cli
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/44,5 MB of archives.
After this operation, 197 MB of additional disk space will be used.
Selecting previously unselected package docker-ce-cli.
(Reading database ... 98034 files and directories currently installed.)
Preparing to unpack .../docker-ce-cli_5%3a19.03.3~3-0~raspbian-stretch_armhf.deb ...
Unpacking docker-ce-cli (5:19.03.3~3-0~raspbian-stretch) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a19.03.3~3-0~raspbian-stretch_armhf.deb ...
Unpacking docker-ce (5:19.03.3~3-0~raspbian-stretch) ...
Processing triggers for systemd (232-25+deb9u12) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up docker-ce-cli (5:19.03.3~3-0~raspbian-stretch) ...
Setting up docker-ce (5:19.03.3~3-0~raspbian-stretch) ...
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 Thu 2019-10-10 14:19:55 CEST; 312ms ago
     Docs: https://docs.docker.com
  Process: 10623 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=killed, signal=TERM)
 Main PID: 10623 (code=killed, signal=TERM)
      CPU: 739ms

Oct 10 14:19:53 raspberrypi systemd[1]: Starting Docker Application Container Engine...
Oct 10 14:19:55 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Linux raspberrypi 4.19.76+ #1272 Fri Oct 4 14:38:35 BST 2019 armv6l GNU/Linux

This is on stretch, but I'm upgrading to Buster as I type this.

[seemethere]

@leifnel you will also need to do a reinstallation/upgrade of the containerd.io package as well

[thaJeztah]

Looks like this is resolved, so let me close this

[seemethere]

Had to rollback the release, will try to re-upload the binaries sometime later this week or early next week.

Sorry for the false alarm guys :/

[leifnel]

Still not OK

`Setting up containerd.io (1.2.6-3) ...
Setting up docker-ce-cli (5:19.03.3~3-0~raspbian-buster) ...
Setting up docker-ce (5:19.03.3~3-0~raspbian-buster) ...
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 Thu 2019-10-10 19:45:41 CEST; 268ms ago
Docs: https://docs.docker.com
Process: 10376 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=killed, signal=TERM)
Main PID: 10376 (code=killed, signal=TERM)

Oct 10 19:45:38 raspberrypi systemd[1]: Starting Docker Application Container Engine...
Oct 10 19:45:41 raspberrypi systemd[1]: docker.service: Main process exited, code=killed, status=15/TERM
Oct 10 19:45:41 raspberrypi systemd[1]: docker.service: Succeeded.
Oct 10 19:45:41 raspberrypi 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-7~deb10u1+rpi1) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
`

[thaJeztah]

@leifnel could you try again? the containerd.io 1.2.10 package should be back up again (which is where the problem was)

[boomam]

Same issue on 3x RPi-ZeroW's today.
Fresh install of buster. Tried a few of the suggestions above, but no luck.
I'm trying to build a mini-cluster so i can test here if it helps move the diagnosis along - let me know.

Does anyone know where i can get containerd.io 1.2.10 package from? The links above are dead...
Thats the only bit i've not been able to test.

[StefanScherer]

@leifnel @boomam The containerd.io 1.2.10-2 package is back online. Now you're ready to go.

[carlos-sarmiento]

@thaJeztah I'm still seeing the segmentation fault error on a brand new Raspberry Pi Zero W. I have containerd.io 1.2.10-3 installed, but starting the containerd.service or docker.service fails with a SEGV

[nidhishdhrugmail]

@thaJeztah I'm still seeing the segmentation fault error on a brand new Raspberry Pi Zero W. I have containerd.io 1.2.10-3 installed, but starting the containerd.service or docker.service fails with a SEGV

Have you ever figured out the reason for this error and fixed it? i am running into the same issue with Pi Zero

[Lazarus404]

Me too

[StefanScherer]

I've updated my Pi0 to the latest releases and it still works

$ dpkg -l |grep container
ii  containerd.io                  1.2.13-1                            armhf        An open and reliable container runtime
ii  docker-ce                      5:19.03.7~3-0~raspbian-buster       armhf        Docker: the open-source application container engine
ii  docker-ce-cli                  5:19.03.7~3-0~raspbian-buster       armhf        Docker CLI: the open-source application container engine
$ uname -a
Linux pi0 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux