Hi all; hope you can assist. Last night I finally did an update of Immich which is the only app I run under Docker on a Ubuntu machine. That upgrade seemed to go okay and confirmed I could talk to the Immich server afterward. Then I decided to do an apt update and apt upgrade; which seemed to work fine until it got to Docker, then it got stuck.
After multiple reboots and killing off the Immich server images; I seemed to get the Docker to upgrade. But then Immich wouldn’t start. Eventually I checked and realized that even Hello-world wouldn’t start. It just locks up.
I’ve tried reinstalling the docker components. Doesn’t seem to make a difference.
Here’s the Docker version output.
DEBU[2026-01-12T12:10:57.764056427-04:00] handling HEAD request method=HEAD module=api request-url=/_ping vars="map[]"
DEBU[2026-01-12T12:10:57.765694840-04:00] handling GET request method=GET module=api request-url=/v1.49/version vars="map[version:1.49]"
Client: Docker Engine - Community
Version: 28.1.1
API version: 1.49
Go version: go1.23.8
Git commit: 4eba377
Built: Fri Apr 18 09:52:20 2025
OS/Arch: linux/arm64
Context: default
Server: Docker Engine - Community
Engine:
Version: 28.1.1
API version: 1.49 (minimum version 1.24)
Go version: go1.23.8
Git commit: 01f442b
Built: Fri Apr 18 09:52:20 2025
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0
rimelek
(Ákos Takács)
January 12, 2026, 5:39pm
2
Please, show how you run the hello world container mentioned in the title. I’m not sure how immich is relevant when the problem is with running “hello-world”. If anything runs automatically not directly executing Docker commands, try the docker commands so see if it is a Docker issue or some kind of compatibility issue between Docker and another application.
When you share how you ran the hello-world container and what the error message, is, please, use MarkDown to format the command and the output. (3 backticks before and after the code block: How to format your forum posts ) Or use the </> button above the message composer.
Hope this helps… this was right after a reboot.
Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 4.19.219-odroid-arm64 aarch64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
_ _ _ _ _
| | | | __ _ _ __ __| | | _____ _ __ _ __ ___| |
| |_| |/ _` | '__/ _` | |/ / _ \ '__| '_ \ / _ \ |
| _ | (_| | | | (_| | < __/ | | | | | __/ |
|_| |_|\__,_|_| \__,_|_|\_\___|_| |_| |_|\___|_|
___ ____ ____ ___ ___ ____ __ __ _
/ _ \| _ \| _ \ / _ \_ _| _ \ | \/ / |
| | | | | | | |_) | | | | || | | |_____| |\/| | |
| |_| | |_| | _ <| |_| | || |_| |_____| | | | |
\___/|____/|_| \_\\___/___|____/ |_| |_|_|
Welcome to Ubuntu 20.04.6 LTS
Monday, 12 January 2026, 01:46:20 PM
Up time: 0 days, 00:00:19
Free memory: 7068096 / 7645920 kB
IP: 192.168.1.100
[!] Please visit 'https://forum.odroid.com' if you need any further assistance.
Last login: Mon Jan 12 13:31:23 2026 from 192.168.1.140
brian@Kylie:~$ sudo systemctl status docker
[sudo] password for brian:
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2026-01-12 13:46:17 AST; 27s ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 401 (dockerd)
Tasks: 26
Memory: 113.5M
CGroup: /system.slice/docker.service
└─401 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.454577502-04:00" level=warning msg="WARNING: No blkio thr>
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.454685127-04:00" level=warning msg="WARNING: No blkio thr>
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.454718085-04:00" level=warning msg="WARNING: No blkio thr>
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.454745794-04:00" level=warning msg="WARNING: No blkio thr>
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.454835044-04:00" level=info msg="Docker daemon" commit=01>
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.455679711-04:00" level=info msg="Initializing buildkit"
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.533310593-04:00" level=info msg="Completed buildkit initi>
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.557749346-04:00" level=info msg="Daemon has completed ini>
Jan 12 13:46:17 Kylie dockerd[401]: time="2026-01-12T13:46:17.558142512-04:00" level=info msg="API listen on /run/docke>
Jan 12 13:46:17 Kylie systemd[1]: Started Docker Application Container Engine.
brian@Kylie:~$ ps -ax | grep docker
401 ? Ssl 0:01 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
963 pts/0 S+ 0:00 grep --color=auto docker
brian@Kylie:~$ sudo docker run hello-world
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF: unknown
Run 'docker run --help' for more information
brian@Kylie:~$ sudo docker run hello-world
^C^C^C
got 3 SIGTERM/SIGINTs, forcefully exiting
So; the first time, it complains… the second time, it just stopped and looked at me stupidly (had to break out of it).
Oh; and noticed that there were three new logs in the Docker status:
Jan 12 13:50:03 Kylie dockerd[401]: time="2026-01-12T13:50:03.105918779-04:00" level=error msg="copy stream failed" err>
Jan 12 13:50:03 Kylie dockerd[401]: time="2026-01-12T13:50:03.105919071-04:00" level=error msg="copy stream failed" err>
Jan 12 13:50:03 Kylie dockerd[401]: time="2026-01-12T13:50:03.154374448-04:00" level=error msg="Handler for POST /v1.49>
meyay
(Metin Y.)
January 12, 2026, 6:12pm
5
Here is a rather old issue that has some suggestions on how to fix the issue:
opened 07:37AM - 20 Apr 20 UTC
area/runtime
kind/bug
version/19.03
**Description**
Intermittently containers cannot be started and docker return… s the following error:
`docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused \"EOF\"": unknown.`
Restarting the machine resolves the issue.
**Steps to reproduce the issue:**
1. docker run --rm -it img /bin/bash
**Describe the results you received:**
`docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused \"EOF\"": unknown.`
**Describe the results you expected:**
Container should start
**Additional information you deem important (e.g. issue happens only occasionally):**
The issue happens only occasionally.
It appears to be connected to https://github.com/moby/moby/issues/37722 and https://github.com/docker/for-linux/issues/856
Feel free to close if there's nothing Docker can do about it.
**Output of `docker version`:**
```
Client: Docker Engine - Community
Version: 19.03.8
API version: 1.40
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:27:04 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.8
API version: 1.40 (minimum version 1.12)
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:25:42 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
```
**Output of `docker info`:**
```
Client:
Debug Mode: false
Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 19
Server Version: 19.03.8
Storage Driver: overlay2
Backing Filesystem: <unknown>
Supports d_type: true
Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-1062.18.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 6.492GiB
Name: fs2
ID: K2B7:KJGO:JNN3:PQWZ:E7AS:YUUY:YCUH:ALUD:2QXI:TEPE:Q6V3:NIEZ
Docker Root Dir: /data/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: true
```
**Additional environment details (AWS, VirtualBox, physical, etc.):**
VM
`/var/log/messages` entries
```
Apr 20 09:13:21 xxx kernel: runc:[1:CHILD]: page allocation failure: order:4, mode:0xc0d0
Apr 20 09:13:21 xxx kernel: CPU: 1 PID: 3522 Comm: runc:[1:CHILD] Kdump: loaded Tainted: G ------------ T 3.10.0-1062.18.1.el7.x86_64 #1
Apr 20 09:13:21 xxx kernel: Hardware name: OpenStack Foundation OpenStack Nova, BIOS 2:1.10.2-58953eb7 04/01/2014
Apr 20 09:13:21 xxx kernel: Call Trace:
Apr 20 09:13:21 xxx kernel: [<ffffffffa6d7b416>] dump_stack+0x19/0x1b
Apr 20 09:13:21 xxx kernel: [<ffffffffa67c3fc0>] warn_alloc_failed+0x110/0x180
Apr 20 09:13:21 xxx kernel: [<ffffffffa6d7698a>] __alloc_pages_slowpath+0x6bb/0x729
Apr 20 09:13:21 xxx kernel: [<ffffffffa67c8636>] __alloc_pages_nodemask+0x436/0x450
Apr 20 09:13:21 xxx kernel: [<ffffffffa6816c58>] alloc_pages_current+0x98/0x110
Apr 20 09:13:21 xxx kernel: [<ffffffffa67e3658>] kmalloc_order+0x18/0x40
Apr 20 09:13:21 xxx kernel: [<ffffffffa6822216>] kmalloc_order_trace+0x26/0xa0
Apr 20 09:13:21 xxx kernel: [<ffffffffa68261a1>] __kmalloc+0x211/0x230
Apr 20 09:13:21 xxx kernel: [<ffffffffa683f041>] memcg_alloc_cache_params+0x81/0xb0
Apr 20 09:13:21 xxx kernel: [<ffffffffa67e3304>] do_kmem_cache_create+0x74/0xf0
Apr 20 09:13:21 xxx kernel: [<ffffffffa67e3482>] kmem_cache_create+0x102/0x1b0
Apr 20 09:13:21 xxx kernel: [<ffffffffc069bdd1>] nf_conntrack_init_net+0xf1/0x260 [nf_conntrack]
Apr 20 09:13:21 xxx kernel: [<ffffffffc069c6d4>] nf_conntrack_pernet_init+0x14/0x150 [nf_conntrack]
Apr 20 09:13:21 xxx kernel: [<ffffffffa6c44054>] ops_init+0x44/0x150
Apr 20 09:13:21 xxx kernel: [<ffffffffa6c44203>] setup_net+0xa3/0x160
Apr 20 09:13:21 xxx kernel: [<ffffffffa6c449a5>] copy_net_ns+0xb5/0x180
Apr 20 09:13:21 xxx kernel: [<ffffffffa66cb599>] create_new_namespaces+0xf9/0x180
Apr 20 09:13:21 xxx kernel: [<ffffffffa66cb7da>] unshare_nsproxy_namespaces+0x5a/0xc0
Apr 20 09:13:21 xxx kernel: [<ffffffffa669afeb>] SyS_unshare+0x1cb/0x340
Apr 20 09:13:21 xxx kernel: [<ffffffffa6d8dede>] system_call_fastpath+0x25/0x2a
Apr 20 09:13:21 xxx kernel: Mem-Info:
Apr 20 09:13:21 xxx kernel: active_anon:58019 inactive_anon:86369 isolated_anon:0#012 active_file:75955 inactive_file:1180913 isolated_file:0#012 unevictable:6102 dirty:95 writeback:0 unstable:0#012 slab_reclaimable:90514 slab_unreclaimable:48526#012 mapped:35231 shmem:143 pagetables:3532 bounce:0#012 free:62074 free_pcp:0 free_cma:0
Apr 20 09:13:21 xxx kernel: Node 0 DMA free:15908kB min:156kB low:192kB high:232kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15908kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Apr 20 09:13:21 xxx kernel: lowmem_reserve[]: 0 2830 6628 6628
Apr 20 09:13:21 xxx kernel: Node 0 DMA32 free:127088kB min:28792kB low:35988kB high:43188kB active_anon:76456kB inactive_anon:137404kB active_file:221232kB inactive_file:2012980kB unevictable:4900kB isolated(anon):0kB isolated(file):0kB present:3129200kB managed:2898768kB mlocked:4900kB dirty:184kB writeback:0kB mapped:107104kB shmem:304kB slab_reclaimable:155508kB slab_unreclaimable:62240kB kernel_stack:1584kB pagetables:4852kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Apr 20 09:13:21 xxx kernel: lowmem_reserve[]: 0 0 3798 3798
Apr 20 09:13:21 xxx kernel: Node 0 Normal free:105300kB min:38632kB low:48288kB high:57948kB active_anon:155620kB inactive_anon:208072kB active_file:82588kB inactive_file:2710672kB unevictable:19508kB isolated(anon):0kB isolated(file):0kB present:4022272kB managed:3892156kB mlocked:19508kB dirty:196kB writeback:0kB mapped:33820kB shmem:268kB slab_reclaimable:206548kB slab_unreclaimable:131864kB kernel_stack:2256kB pagetables:9276kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Apr 20 09:13:21 xxx kernel: lowmem_reserve[]: 0 0 0 0
Apr 20 09:13:21 xxx kernel: Node 0 DMA: 1*4kB (U) 0*8kB 0*16kB 1*32kB (U) 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15908kB
Apr 20 09:13:21 xxx kernel: Node 0 DMA32: 9256*4kB (UEM) 8488*8kB (UEM) 1288*16kB (UEM) 25*32kB (UM) 9*64kB (M) 1*128kB (M) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 127040kB
Apr 20 09:13:21 xxx kernel: Node 0 Normal: 14942*4kB (UEM) 5699*8kB (UEM) 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 105360kB
Apr 20 09:13:21 xxx kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Apr 20 09:13:21 xxx kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Apr 20 09:13:21 xxx kernel: 1260617 total pagecache pages
Apr 20 09:13:21 xxx kernel: 1355 pages in swap cache
Apr 20 09:13:21 xxx kernel: Swap cache stats: add 45752, delete 44397, find 6635088/6637528
Apr 20 09:13:21 xxx kernel: Free swap = 4148988kB
Apr 20 09:13:21 xxx kernel: Total swap = 4194300kB
Apr 20 09:13:21 xxx kernel: 1791866 pages RAM
Apr 20 09:13:21 xxx kernel: 0 pages HighMem/MovableOnly
Apr 20 09:13:21 xxx kernel: 90158 pages reserved
Apr 20 09:13:21 xxx kernel: kmem_cache_create(nf_conntrack_ffff9b3827d29480) failed with error -12
Apr 20 09:13:21 xxx kernel: CPU: 1 PID: 3522 Comm: runc:[1:CHILD] Kdump: loaded Tainted: G ------------ T 3.10.0-1062.18.1.el7.x86_64 #1
Apr 20 09:13:21 xxx kernel: Hardware name: OpenStack Foundation OpenStack Nova, BIOS 2:1.10.2-58953eb7 04/01/2014
Apr 20 09:13:21 xxx kernel: Call Trace:
Apr 20 09:13:21 xxx kernel: [<ffffffffa6d7b416>] dump_stack+0x19/0x1b
Apr 20 09:13:21 xxx kernel: [<ffffffffa67e3507>] kmem_cache_create+0x187/0x1b0
Apr 20 09:13:21 xxx kernel: [<ffffffffc069bdd1>] nf_conntrack_init_net+0xf1/0x260 [nf_conntrack]
Apr 20 09:13:21 xxx kernel: [<ffffffffc069c6d4>] nf_conntrack_pernet_init+0x14/0x150 [nf_conntrack]
Apr 20 09:13:21 xxx kernel: [<ffffffffa6c44054>] ops_init+0x44/0x150
Apr 20 09:13:21 xxx kernel: [<ffffffffa6c44203>] setup_net+0xa3/0x160
Apr 20 09:13:21 xxx kernel: [<ffffffffa6c449a5>] copy_net_ns+0xb5/0x180
Apr 20 09:13:21 xxx kernel: [<ffffffffa66cb599>] create_new_namespaces+0xf9/0x180
Apr 20 09:13:21 xxx kernel: [<ffffffffa66cb7da>] unshare_nsproxy_namespaces+0x5a/0xc0
Apr 20 09:13:21 xxx kernel: [<ffffffffa669afeb>] SyS_unshare+0x1cb/0x340
Apr 20 09:13:21 xxx kernel: [<ffffffffa6d8dede>] system_call_fastpath+0x25/0x2a
Apr 20 09:13:21 xxx kernel: Unable to create nf_conn slab cache
Apr 20 09:13:21 xxx containerd: time="2020-04-20T09:13:21.565957368+02:00" level=info msg="shim reaped" id=a8da2d54ebf451c4ee6118a276b2e4a10f3d6f61ebc52b853c34419ba4c132bb
Apr 20 09:13:21 xxx dockerd: time="2020-04-20T09:13:21.579186951+02:00" level=error msg="stream copy error: reading from a closed fifo"
```
1 Like
In my case, it’s 100% consistent. I can’t run any container, it seems. It was pointed out that I’m running ubuntu 20.*, is that old enough that Docker would have issues?
meyay
(Metin Y.)
January 12, 2026, 7:41pm
7
I have an old vm with Ubuntu 20 and the same docker engine version: this is not the reason it’s not running.
Ubuntu 20.04 and Docker 28.1.1 are EOL and have no support whatsoever.
It must be a configuration you applied to the system. Could be the result of “hardening” the system.
Did you try the suggestions from the GitHub issue I shared?
system
(system)
Closed
February 11, 2026, 7:42pm
8
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.