Cannot run hello-world after upgrade

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

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>

Here is a rather old issue that has some suggestions on how to fix the issue:

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?

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?

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