You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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:
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
Description
When I am drying to deploy a jellystat container (with docker-compose), I get this error
docker-compose content doesn't matter, because even the most bare one produces the same error:
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
Additional Info
No response
The text was updated successfully, but these errors were encountered: