Docker containers updates are very slow, if not impossible

General
1

Hello

I’m running Debian, and for a few days now, my docker container updates have been very slow, if not impossible.

I don’t understand where the problem comes from. Can anyone help me?

My hard disk is 22% full.

/etc/resolv.conf :

nameserver 1.1.1.1
nameserver 1.0.0.1

Example of docker-compose.yml :

services:
  flaresolverr:
    image: ghcr.io/flaresolverr/flaresolverr:latest
    container_name: flaresolverr
    environment:
      - LOG_LEVEL=${LOG_LEVEL:-info}
      - LOG_HTML=${LOG_HTML:-false}
      - CAPTCHA_SOLVER=${CAPTCHA_SOLVER:-none}
      - TZ=Europe/Paris
    ports:
      - "${PORT:-8191}:8191"
    restart: unless-stopped

If anyone can help me ? if you want any informations, ask it :slight_smile:

2

What is a Docker container update?

3

Sorry, my english is not really good :stuck_out_tongue:

If i go to /home/machou/docker/flaresolverr/

I do a docker compose up -d

This is an update :stuck_out_tongue:

4

Oh, I see. “up” doesn’t mean “update”. It just “brings up” the project which can include building a new Docker image, creating and starting the container with or without mounted volumes.

If it is slow, the question is what kind of Docker you use, on what platform and how you installed it. Is it Docker Desktop or Docker CE? Is it installed on Linux, Windows or macOS. What the CPU architecture is and whether you needed to emulate a different architetcure or not. If it needs to pull the image, that could also take time, at least the first time. Please share the above details. The output of the below comands could help if you are not sure.

docker info
docker version

Also share the link to the documentation you followed to install Docker.

1 Like
5

It s a Docker ce, on Debian 12 ARM 64.

I have the impression that it’s slow (if not impossible) at certain times, at random. Yet all the other sites/services on my network are working perfectly, only Docker is causing problems.

docker version :

Client: Docker Engine - Community
 Version:           25.0.3
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        4debf41
 Built:             Tue Feb  6 21:14:22 2024
 OS/Arch:           linux/arm64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          25.0.3
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       f417435
  Built:            Tue Feb  6 21:14:22 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info :

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

Server:
 Containers: 4
  Running: 4
  Paused: 0
  Stopped: 0
 Images: 4
 Server Version: 25.0.3
 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: systemd
 Cgroup Version: 2
 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: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.1.0-18-arm64
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType: linux
 Architecture: aarch64
 CPUs: 2
 Total Memory: 973.4MiB
 Name: debian
 ID: 7c6af097-42c5-4299-a157-d9a2b5562043
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Example where is the problem:

1143×385 8.56 KB

6

So the slow part is downloading the image and not running the container. That could be a network issue between you and Docker Hub or any problem with Docker Hub itself sometimes.

7

yes i understand, but how can i find and fix the problem ? :stuck_out_tongue:

8

Run network tests. Download large files from the Internet.

Make sure if your node is a SBC, that your storage (like SD card) is not slow or worn out.

9

You can also try downloading images from other registries. If that is always faster, the problem is probably not on your machine. Then you can try to download other images. from Docker Hub. If that is always faster, something could be with the storage on which the layers of the image are. You can try speedtests like Ookla and trace your network packets, but recognizing the issue is usually not easy, especially for someone who is not familiar with networks. You can still search for tcpdump and tshark or wireshark if you have GUI. There is no one solution for all cases and I’m not good enough to guide you through online when it would take a long time to me as well to find the cause in person. If you are trying to use Docker at work, you can also ask the system administrators if they exist.