Port already allocated despite container down

Docker Engine General
1

hello everyone, im reopening this topic Failed: port is already allocated even with container down, we stopped at the docker packages, because, back then i installed docker via ubuntu packages instead of docker official packages. However, I’m now having the same problem with the official Docker packages. Docker refuses to start container because another container is using that port, even though the container is down. Here are the logs:

root@ip-xxxxxxxx:/data# docker-compose up -d
[+] Running 0/1
⠹ Container proxy  Starting                                                                                                                                                                                           0.2s
Error response from daemon: driver failed programming external connectivity on endpoint proxy (ed0161fb1018fa242e2a62995011a82214a04f5eefbcb87bc776d32a7448d83f): Bind for 0.0.0.0:80 failed: port is already allocated
root@ip-xxxxxxxx:/data# lsof -i :80
root@ip-xxxxxxxx:/data# lsof -i :80
root@ip-xxxxxxxx:/data# ss -tulne | grep 80
tcp    LISTEN  0       4096                0.0.0.0:8081           0.0.0.0:*      ino:24928 sk:4 ↔ 
tcp    LISTEN  0       4096                0.0.0.0:8080           0.0.0.0:*      ino:50371 sk:1001 ↔ 
tcp    LISTEN  0       4096                   [::]:8081              [::]:*      ino:25926 sk:11 v6only:1 ↔ 
tcp    LISTEN  0       4096                   [::]:8080              [::]:*      ino:50377 sk:1003 v6only:1 ↔ 
root@ip-xxxxxxxx:/data# docker-compose down -v
[+] Running 1/0
✔ Container proxy  Removed                                                                                                                                                                                            0.0s
root@ip-xxxxxxxx:/data# ^C
root@ip-xxxxxxxx:/data# docker-compose up -d
[+] Running 1/1
✔ Container proxy  Created                                                                                                                                                                                            0.1s
Error response from daemon: driver failed programming external connectivity on endpoint proxy (89b70318eee9c7b3624d7160e21df120c4f6a1959e8d69f4d3534d3122b83193): Bind for 0.0.0.0:80 failed: port is already allocated

Client: Docker Engine - Community
Version:    27.1.2
Context:    default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version:  v0.16.2
Path:     /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version:  v2.29.1
Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 14
Running: 14
Paused: 0
Stopped: 0
Images: 15
Server Version: 27.1.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8fc6bcff51318944179630522a095cc9dbf9f353
runc version: v1.1.13-0-g58aa920
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
Kernel Version: 5.15.0-1084-aws
Operating System: Ubuntu 20.04.6 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 913.6MiB
Name: ip-xxxxxxxx
ID: 7de4ebad-xxxxxxxxxxxxxxxxxxxxxx
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: xxxxxxxx
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

Client: Docker Engine - Community
Version:           27.1.2
API version:       1.46
Go version:        go1.21.13
Git commit:        d01f264
Built:             Mon Aug 12 11:51:03 2024
OS/Arch:           linux/amd64
Context:           default

Server: Docker Engine - Community
Engine:
Version:          27.1.2
API version:      1.46 (minimum version 1.24)
Go version:       go1.21.13
Git commit:       f9522e5
Built:            Mon Aug 12 11:51:03 2024
OS/Arch:          linux/amd64
Experimental:     true
containerd:
Version:          1.7.20
GitCommit:        8fc6bcff51318944179630522a095cc9dbf9f353
runc:
Version:          1.1.13
GitCommit:        v1.1.13-0-g58aa920
docker-init:
Version:          0.19.0
GitCommit:        de40ad0

dpkg -l ‘docker*’ | grep ‘^ii’
ii  docker-buildx-plugin      0.16.2-1~ubuntu.20.04~focal   amd64        Docker Buildx cli plugin.
ii  docker-ce                 5:27.1.2-1~ubuntu.20.04~focal amd64        Docker: the open-source application container engine
ii  docker-ce-cli             5:27.1.2-1~ubuntu.20.04~focal amd64        Docker CLI: the open-source application container engine
ii  docker-ce-rootless-extras 5:27.1.2-1~ubuntu.20.04~focal amd64        Rootless support for Docker.
ii  docker-compose-plugin     2.29.1-1~ubuntu.20.04~focal   amd64        Docker Compose (V2) plugin for the Docker CLI.

snap list docker
error: no matching snaps installed

The only solution I have is to restart the Docker service, which is not ideal in a production environment.

2

Great that you are using the official repository, but you are still using an Ubuntu version that is not suported anymore with an old Docker version. Since Ubuntu 20.04 reached its enf og life, latest v28 and v29 versions are not available, but v27.5.1 should still be available. I can find those in the APT repository:

If you want to report this as a bug later, we should try to reproduce the issue on a more recent version. Even v25.5.1 was released a year ago and I doubt we will get a new update for that major version,

Youare also using the docker-compose command. On Windows, that is an alias to docker compose (or it was at least), but not with Docker CE, so if you still have the old python-based compose installed, even if you see your compose plugin version is v2, the actual compose you are using could be older, which could break something, although I would expect API call errors, not this issue.

What does docker-compose version return?

Can you also try using docker run and docker rm -f commands like this?

docker run --name test -p 80:80 nginx
docker rm -f test
docker run --name test -p 80:80 nginx
3

I know this is an older ubuntu version, we’re updating slowly, i cant use port 80 im my host because it’s already in use by another container, this is a production enviroment, i used port 90 instead

root@ip-xxxxxxxx:~# docker-compose version
Docker Compose version v2.23.3
root@ip-172-33-13-185:~# docker compose version
Docker Compose version v2.29.1

root@ip-xxxxxxxx:~# docker run --name test -p 90:80 nginx
/docker-entrypoint.sh: Configuration complete; ready for start up
2026/01/16 18:34:11 [notice] 1#1: exit
root@ip-172-33-13-185:~# docker rm -f test
test
root@ip-xxxxxxxx:~# docker run --name test -p 90:80 nginx
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
2026/01/16 18:34:20 [notice] 1#1: exit
4

The socket statics command is not really suited to identify if a process binds a port on the host.

Please use this command instead and share its output:

sudo netstat -tlpn | grep ":80 "

According docker info you run 14 containers one a t3.nano compute node… The whole os and all processes it runs, including the docker engine itself and your 14 containers are sharing ~1 GB ram. Are you sure the machine is not overwhelmed?

Furthermore, it wouldn’t hurt to see you compose file content, to get an idea of what we are dealing with here.

Update: seems ss command is suited after all:

sudo ss -tlpn | grep ":80 "
5

In addition to sharing your compose file (as @meyay wrote) or any compose file that has the same result, you could also try to create a compose file using port forward from port 90 and run the same commands you did with your production service, since it looks like there was no problem with port 90 when using docker run commands..

6

Replying yo @meyay, the output of sudo ss -tlpn | grep ":80 " will return the process because now everything is fine now. As i said this is a prod environment and the reverse proxy uses this port, so when the problem happened, i only had few minutes to collect data before resolving the issue by restarting docker service.

My reverse proxy compose (the one with problems)

version: ‘3.8’

services:

proxy:
container_name: “devoz-proxy”
image: “haproxy:2.8.15”
user: root
ports:
- “80:80”
- “443:443”
- “1936:1936”
restart: always
networks:
- “ozmap_isolated_nw”
volumes:
- /opt/haproxy/:/usr/local/etc/haproxy/
- /opt/haproxy/errors/:/errors/
- /opt/ssl/:/ssl/
environment:
DEBUG: “*”
networks:
ozmap_isolated_nw:
external: true

So i tested with another compose:

version: “3.8”

services:
  nginxproxy:
    container_name: nginx
    image: nginx:latest
    ports:
      - “90:80”
    networks:
      - “ozmap_isolated_nw”
networks:
  ozmap_isolated_nw:
    external: true

root@ip-xxxxxxxxx:~# docker kill nginx
root@ip-xxxxxxxxx:~# docker-compose ps -a

NAME IMAGE COMMAND SERVICE CREATED STATUS PORTSnginx nginx:latest “/docker-entrypoint.…” nginxproxy 7 minutes ago Exited (137) 4 seconds ago
root@ip-xxxxxxxxx:~# docker-compose up -d

[+] Running 1/1 :check_mark: Container nginx Started 0.0s

No problems, i really dont know how to reproduce this behavior, sounds like random, or very specific scenario. The context of the error was, we had to restart the ec2 because it was very slow and had exhausted its resources.

Here is the journalctl

0 5f9ef26ca3fb4e65a3aa3784063e0ef0 Thu 2026-01-15 18:14:54 UTC—Mon 2026-01-19 13:17:21 → last reboot
Jan 15 18:10:28 ip-172-33-13-185 systemd[1]: Stopping Docker Application Container Engine…
– Subject: A stop job for unit docker.service has begun execution
– Defined-By: systemd
– Support: http://www.ubuntu.com/support

– A stop job for unit docker.service has begun execution.

– The job identifier is 147316.
Jan 15 18:10:51 ip-172-33-13-185 dockerd[714]: time=“2026-01-15T18:10:45.200692661Z” level=info msg=“Processing signal ‘terminated’”
Jan 15 18:11:58 ip-172-33-13-185 systemd[1]: docker.service: Killing process 714 (dockerd) with signal SIGKILL.
Jan 15 18:11:58 ip-172-33-13-185 systemd[1]: docker.service: Main process exited, code=killed, status=9/KILL
Jan 15 18:15:43 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:15:43.781491705Z” level=info msg=“Removing stale endpoint devoz-proxy (874034bfbc8726bb2ea779e669e19a362bac614e607ec44e4162319d2daf7efd)”
Jan 15 18:21:50 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:21:50.746692326Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”
Jan 15 18:22:36 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:22:36.138480583Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers"Jan 15 18:22:36 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:22:36.153619568Z” level=warning msg=“Failed to allocate and map port: Bind for 0.0.0.0:80 failed: port is already allocated”
Jan 15 18:22:36 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:22:36.306307856Z” level=error msg=“2c320ec50cd7ca4523baf6aeb441d85a29230ce478bd725cabbbc0d6985212da cleanup: failed to delete container from containerd: NotFound: container "2c320ec50cd7ca4523baf6aeb441d85a29230ce478bd725cabbbc0d6985212da" in namespace "moby": not found”
Jan 15 18:22:36 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:22:36.374659318Z” level=error msg=“Handler for POST /v1.43/containers/2c320ec50cd7ca4523baf6aeb441d85a29230ce478bd725cabbbc0d6985212da/start returned error: driver failed programming external connectivity on endpoint devoz-proxy (d69497c01c8d632a87dd7702ab0fabd00006ce218fd9155992a6f01e464b2936): Bind for 0.0.0.0:80 failed: port is already allocated”
Jan 15 18:22:55 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:22:55.725811484Z” level=info msg=“ignoring event” container=990d9023d0b52e84608d421aed183e22b2c00c169ea27bf0b6413630bbcf3d4b module=libcontainerd namespace=mob
y topic=/tasks/delete type=”*events.TaskDelete"
Jan 15 18:22:56 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:22:56.224332340Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers"Jan 15 18:23:25 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:23:25.115320161Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”
Jan 15 18:23:25 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:23:25.124166609Z” level=warning msg=“Failed to allocate and map port: Bind for 0.0.0.0:80 failed: port is already allocated"Jan 15 18:23:25 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:23:25.261664595Z” level=error msg=“Handler for POST /v1.43/containers/cd0fd7060baa72573ad6ddec766f1170bea03d30a7f19a4735b90d710f0bbff2/start returned error: dr
iver failed programming external connectivity on endpoint devoz-proxy (689de3d47529c354579fdb19a2cf687d95f509eb8c4fbeac1a0e3d2ef9b0cc0d): Bind for 0.0.0.0:80 failed: port is already allocated”
Jan 15 18:24:00 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:24:00.773598513Z” level=info msg=“ignoring event” container=990d9023d0b52e84608d421aed183e22b2c00c169ea27bf0b6413630bbcf3d4b module=libcontainerd namespace=mob
y topic=/tasks/delete type=”*events.TaskDelete"Jan 15 18:24:01 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:24:01.259127534Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”
Jan 15 18:24:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:24:35.365226290Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers"Jan 15 18:24:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:24:35.380594537Z” level=warning msg=“Failed to allocate and map port: Bind for 0.0.0.0:80 failed: port is already allocated”
Jan 15 18:24:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:24:35.514454801Z” level=error msg=“Handler for POST /v1.43/containers/cd0fd7060baa72573ad6ddec766f1170bea03d30a7f19a4735b90d710f0bbff2/start returned error: dr
iver failed programming external connectivity on endpoint devoz-proxy (ed0161fb1018fa242e2a62995011a82214a04f5eefbcb87bc776d32a7448d83f): Bind for 0.0.0.0:80 failed: port is already allocated”
Jan 15 18:25:05 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:05.427204441Z” level=info msg=“ignoring event” container=990d9023d0b52e84608d421aed183e22b2c00c169ea27bf0b6413630bbcf3d4b module=libcontainerd namespace=moby topic=/tasks/delete type=”*events.TaskDelete”
Jan 15 18:25:05 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:05.866990172Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”
Jan 15 18:25:17 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:17.520489278Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”
Jan 15 18:25:17 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:17.529725109Z” level=warning msg=“Failed to allocate and map port: Bind for 0.0.0.0:80 failed: port is already allocated”
Jan 15 18:25:17 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:17.741545857Z” level=error msg=“Handler for POST /v1.43/containers/94c480f63bacf732ad7d0fe16c1b4cfa9a1667731982855899626c27e4b76b3e/start returned error: dr
iver failed programming external connectivity on endpoint devoz-proxy (89b70318eee9c7b3624d7160e21df120c4f6a1959e8d69f4d3534d3122b83193): Bind for 0.0.0.0:80 failed: port is already allocated”
Jan 15 18:25:33 ip-172-33-13-185 systemd[1]: Stopping Docker Application Container Engine… # manual restart docker
Jan 15 18:25:34 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:34.800383645Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=c9eb0b1a7e07afc46db72bf3f99ba0e2fea02988c44500dd22aeae9e86c4b13a daemonShuttingDown=true error=“restart canceled” execDuration=9m48.759099498s exitStatus=“{143 2026-01-15 18:25:34.598177725 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:34 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:34.956062563Z” level=info msg=“ignoring event” container=d38e755ff7f2ade5743709818840a5b5414bb75257fb3ff4890db747efd72521 module=libcontainerd namespace=moby topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:35.057294771Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=d38e755ff7f2ade5743709818840a5b5414bb75257fb3ff4890db747efd72521 daemonShuttingDown=true error=“restart canceled” execDuration=9m49.606260329s exitStatus=“{0 2026-01-15 18:25:34.856535704 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:35.238302672Z” level=info msg=“ignoring event” container=5b9a50400ecff079c7841cf4efabc29d217fb353cd65a38cf097a8f70e46cc18 module=libcontainerd namespace=moby topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:35.375621707Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=5b9a50400ecff079c7841cf4efabc29d217fb353cd65a38cf097a8f70e46cc18 daemonShuttingDown=true error=“restart canceled” execDuration=9m50.34974831s exitStatus=“{0 2026-01-15 18:25:35.086633594 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:35.762676976Z” level=info msg=“ignoring event” container=ef3088e8033f5b935ea659a5ab4751466d2bb7ed5111e42089b89445dd16878d module=libcontainerd namespace=moby topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:35 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:35.839502235Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=ef3088e8033f5b935ea659a5ab4751466d2bb7ed5111e42089b89445dd16878d daemonShuttingDown=true error=“restart canceled” execDuration=9m50.435908582s exitStatus=“{0 2026-01-15 18:25:35.528535459 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:36 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:36.785015809Z” level=info msg=“ignoring event” container=de021ef52d7caeb6762d99ee09006a684c1176bd36d475da4a14ec092d392be1 module=libcontainerd namespace=moby topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:36 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:36.832902752Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=de021ef52d7caeb6762d99ee09006a684c1176bd36d475da4a14ec092d392be1 daemonShuttingDown=true error=“restart canceled” execDuration=9m51.276333603s exitStatus=“{0 2026-01-15 18:25:36.726793761 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:36 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:36.948000755Z” level=info msg=“ignoring event” container=7e4de31c93e714fff55f58cfc6994fbe5d02503f82c12ab09eaf00aed8087123 module=libcontainerd namespace=moby topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:37 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:37.036351042Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=7e4de31c93e714fff55f58cfc6994fbe5d02503f82c12ab09eaf00aed8087123 daemonShuttingDown=true error=“restart canceled” execDuration=9m51.088430839s exitStatus=“{1 2026-01-15 18:25:36.864220794 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:37 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:37.588878066Z” level=info msg=“ignoring event” container=36ae64323089a5a9ca33e58d2a39dfaa2a467255a0a576dd46480e3db23fdc19 module=libcontainerd namespace=moby topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:37 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:37.616519337Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=36ae64323089a5a9ca33e58d2a39dfaa2a467255a0a576dd46480e3db23fdc19 daemonShuttingDown=true error=“restart canceled” execDuration=9m52.992341862s exitStatus=“{1 2026-01-15 18:25:37.563151054 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:40 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:40.026925047Z” level=info msg=“ignoring event” container=40b0e988e06145f0c21abacff1a0739af829b2d845ce4a90dfebe5939168f0f6 module=libcontainerd namespace=moby topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:40 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:40.061800759Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=40b0e988e06145f0c21abacff1a0739af829b2d845ce4a90dfebe5939168f0f6 daemonShuttingDown=true error=“restart canceled” execDuration=9m54.154675997s exitStatus=“{0 2026-01-15 18:25:39.9986036 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:43 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:43.486459137Z” level=info msg=“Container failed to exit within 10s of signal 15 - using the force” container=990d9023d0b52e84608d421aed183e22b2c00c169ea27bf
0b6413630bbcf3d4b
Jan 15 18:25:43 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:43.534052469Z” level=info msg=“ignoring event” container=990d9023d0b52e84608d421aed183e22b2c00c169ea27bf0b6413630bbcf3d4b module=libcontainerd namespace=mob
y topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:43 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:43.560975484Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=990d9023d0b52e84608d421aed183e22b2c00c169ea27bf0b6413630b
bcf3d4b daemonShuttingDown=true error=“restart canceled” execDuration=37.493817341s exitStatus=“{137 2026-01-15 18:25:43.51546101 +0000 UTC}” hasBeenManuallyStopped=false restartCount=8
Jan 15 18:25:43 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:43.575041568Z” level=info msg=“Container failed to exit within 10s of signal 15 - using the force” container=b453fc13c2703e9e0bbbc63c2687471998a75207878e641
4206b4d7caf9c7d4b
Jan 15 18:25:43 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:43.774468498Z” level=info msg=“ignoring event” container=b453fc13c2703e9e0bbbc63c2687471998a75207878e6414206b4d7caf9c7d4b module=libcontainerd namespace=mob
y topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:25:43 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:43.826605136Z” level=warning msg=“ShouldRestart failed, container will not be restarted” container=b453fc13c2703e9e0bbbc63c2687471998a75207878e6414206b4d7ca
f9c7d4b daemonShuttingDown=true error=“restart canceled” execDuration=9m58.567299795s exitStatus=“{137 2026-01-15 18:25:43.702815126 +0000 UTC}” hasBeenManuallyStopped=false restartCount=0
Jan 15 18:25:44 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:44.056086664Z” level=info msg=“stopping event stream following graceful shutdown” error=“” module=libcontainerd namespace=moby
Jan 15 18:25:44 ip-172-33-13-185 dockerd[703]: time=“2026-01-15T18:25:44.064255019Z” level=info msg=“Daemon shutdown complete”
Jan 15 18:25:44 ip-172-33-13-185 systemd[1]: docker.service: Succeeded.
Jan 15 18:25:44 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:44.453349941Z” level=info msg=“Starting up”
Jan 15 18:25:44 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:44.453504110Z” level=warning msg=“Running experimental build”
Jan 15 18:25:44 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:44.454977062Z” level=info msg=“detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf”
Jan 15 18:25:44 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:44.554638832Z” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Jan 15 18:25:45 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:45.271638005Z” level=info msg=“Loading containers: start.”
Jan 15 18:25:45 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:45.648439710Z” 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
Jan 15 18:25:49 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:49.943881480Z” level=info msg=“Loading containers: done.”
Jan 15 18:25:50 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:50.026626428Z” level=info msg=“Docker daemon” commit=f9522e5 containerd-snapshotter=false storage-driver=overlay2 version=27.1.2
Jan 15 18:25:50 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:50.027422524Z” level=info msg=“metrics API listening on [::]:9323”
Jan 15 18:25:50 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:50.029200914Z” level=info msg=“Daemon has completed initialization”
Jan 15 18:25:50 ip-172-33-13-185 systemd[1]: Started Docker Application Container Engine.
– Subject: A start job for unit docker.service has finished successfully
– Defined-By: systemd
– Support: http://www.ubuntu.com/support

– A start job for unit docker.service has finished successfully.

– The job identifier is 776.
Jan 15 18:25:50 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:25:50.210238825Z” level=info msg=“API listen on /run/docker.sock”
Jan 15 18:26:33 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:26:33.387485544Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”
Jan 15 18:27:03 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:27:03.408720179Z” level=info msg=“ignoring event” container=990d9023d0b52e84608d421aed183e22b2c00c169ea27bf0b6413630bbcf3d4b module=libcontainerd namespace=mo
by topic=/tasks/delete type=“*events.TaskDelete”
Jan 15 18:27:04 ip-172-33-13-185 dockerd[5662]: time=“2026-01-15T18:27:04.336235824Z” level=info msg=“No non-localhost DNS nameservers are left in resolv.conf. Using default external servers”

No errors beyond this point.