Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: “docker-entrypoint.sh”: executable file not found in $PATH: unknown #47847

Open
lockheed opened this issue May 20, 2024 · 0 comments

Comments

@lockheed
Copy link

lockheed commented May 20, 2024

Description

When I am drying to deploy a jellystat container (with docker-compose), I get this error

[+] Running 3/3
Network jellystat Created 0.0s
Container jellystat.kv-db Started 0.2s
Container jellystat.kv Created 0.2s
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: exec: “docker-entrypoint.sh”: executable file not found in $PATH: unknown

docker-compose content doesn't matter, because even the most bare one produces the same error:

    services:
     jellystat:
      container_name: jellystat
      image: cyfershepard/jellystat:latest

There is one thing I can think of that happened between this working and not-working:
I accidentally deleted zfs datasets for previous jellystat container, but I then recreated them, deleted the container properly (which also deletes datasets in the right way) and now trying to start from scratch. This has worked for every other container affected and everything else is working beautifully, including (re)creation.

Reproduce

As above

Expected behavior

No response

docker version

Client:
 Version:           26.1.2
 API version:       1.45
 Go version:        go1.22.3
 Git commit:        211e74b240
 Built:             Thu May  9 14:45:05 2024
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          26.1.2
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.22.3
  Git commit:       ef1912d8b6
  Built:            Thu May  9 14:45:05 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.16
  GitCommit:        83031836b2cf55637d7abf847b17134c51b38e53.m
 runc:
  Version:          1.1.12
  GitCommit:        
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    26.1.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  0.14.0
    Path:     /usr/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  2.27.0
    Path:     /usr/lib/docker/cli-plugins/docker-compose

Server:
 Containers: 49
  Running: 48
  Paused: 0
  Stopped: 1
 Images: 82
 Server Version: 26.1.2
 Storage Driver: zfs
  Zpool: fastraid
  Zpool Health: ONLINE
  Parent Dataset: fastraid/docker
  Space Used By Parent: 15526264832
  Space Available: 3183010299904
  Parent Quota: no
  Compression: zstd
 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: 83031836b2cf55637d7abf847b17134c51b38e53.m
 runc version: 
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.6.30-2-lts
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 62.69GiB
 Name: blackrock
 ID: DIQD:MMSZ:USSX:SAZ2:M36C:B3XP:WPVO:F3CW:KBUM:5RAY:N4Z3:53TW
 Docker Root Dir: /z/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional Info

No response

@lockheed lockheed added kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. status/0-triage labels May 20, 2024
@thaJeztah thaJeztah added version/26.1 area/storage/zfs kind/question and removed kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants