desktop-linux icon indicating copy to clipboard operation
desktop-linux copied to clipboard

DinD - container failed to start due to network issue

Open acnicholls opened this issue 1 year ago • 0 comments

Description

am using github actions to try to deploy a compose container. everything works until I try to start the container. volumes are created, the containers are created, but when the UI client service tries to start, it bombs out with the following error;

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: 
error during container init: 
error running hook #0: 
error running hook: 
exit status 1, stdout: , stderr: 
failed to add interface vethfd935d1 to sandbox: 
error setting interface "vethfd935d1" IPv6 to <nil>: 
failed to configure ipv6: 
failed to disable IPv6 on container's interface eth0: 
unknown

Reproduce

  1. setup debian10 or ubuntu 22.04 docker host inside VM that uses container system (centos /w docker v19.01.10)
  2. install docker & docker compose
  3. create/download docker-compose file
  4. run docker compose -f <compose file> up -d
  5. see error

Expected behavior

container should run.

docker version

Client: Docker Engine - Community
 Version:           27.2.1
 API version:       1.47
 Go version:        go1.22.7
 Git commit:        9e34c9b
 Built:             Fri Sep  6 12:08:10 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          27.2.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.7
  Git commit:       8b539b8
  Built:            Fri Sep  6 12:08:10 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.21
  GitCommit:        472731909fa34bd7bc9c087e4c27943f9835f111
 runc:
  Version:          1.1.13
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client: Docker Engine - Community
 Version:    27.2.1
 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.2
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 4
  Running: 0
  Paused: 0
  Stopped: 4
 Images: 8
 Server Version: 27.2.1
 Storage Driver: vfs
 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: 472731909fa34bd7bc9c087e4c27943f9835f111
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
 Kernel Version: 3.10.0-1062.el7.x86_64
 Operating System: Ubuntu 22.04.4 LTS (containerized)
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 8GiB
 Name: ubuntu
 ID: 4a203439-2c04-42f9-ae6b-d5c3c4c7a861
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Diagnostics ID

I don't have one. I'm using docker in linux with no desktop

Additional Info

No response

acnicholls avatar Sep 10 '24 04:09 acnicholls