Docker container could not able to start failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process

Question

Docker container could not able to start failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process

sachingade20 opened this issue 2 years ago · comments

Docker Image ghcr.io/silverton-io/buz is not functional or not built properly

docker-compose -f examples/qui [+] Running 25/25
⠿ redpanda-3 Pulled ⠿ 7bc891379e23 Pull complete ⠿ 1c6096033ccb Pull complete ⠿ faf8b94c4e98 Pull complete ⠿ f2513e35e4c0 Pull complete ⠿ 5c773fd6c7ce Pull complete ⠿ 25d02e628d66 Pull complete ⠿ 028dd9165344 Pull complete ⠿ c1f087ade85b Pull complete ⠿ console Pulled ⠿ 63b65145d645 Already exists ⠿ 78a7f2a538a1 Pull complete ⠿ 7951c7c4f5bc Pull complete ⠿ 7bcc25627bb0 Pull complete ⠿ e1ac679e7cca Pull complete ⠿ 46dc7bdf88eb Pull complete ⠿ sample-ui Pulled ⠿ 50783e0dfb64 Pull complete ⠿ 8ff7648aa566 Pull complete ⠿ 8c6a8f49a297 Pull complete ⠿ 7355b61ca2f7 Pull complete ⠿ 73bea7abc5c8 Pull complete ⠿ 1e0c520cdc18 Pull complete ⠿ redpanda-1 Pulled ⠿ redpanda-2 Pulled [+] Running 6/7
⠿ Network quickstart_default Created ⠿ Container redpanda-2 ⠿ Container sample-ui ⠿ Container redpanda-3 ⠿ Container redpanda-1 ⠿ Container console ⠿ Container buz Error response from daemon: ckstart/docker-compose.yml up -d
11.3s
3.2s
3.8s
3.9s
4.0s
4.2s
5.0s
8.1s
8.4s
11.1s
0.0s
2.6s
2.8s
5.5s
6.1s
6.9s
4.1s
0.4s
0.5s
0.6s
0.6s
1.2s
1.3s
11.3s
11.3s
0.1s
Healthy 7.0s
Started 6.0s
Healthy 7.5s
Healthy 7.0s
Started 3.7s
Starting 3.9s
failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./buz": stat ./buz: no such file or directory: unknown

Jake Thomas · Answer 1 · Tue Mar 14 2023 09:58:25 GMT+0800 (China Standard Time)

Thanks @sachingade20, will take a peek right now!

Jake Thomas · Answer 2 · Tue Mar 14 2023 10:42:33 GMT+0800 (China Standard Time)

@sachingade20 this one has been fixed, thanks again for the 🐛 🗒️ .

pinging @taborwells as well, since you mentioned this today :)

Sachin Gade · Answer 3 · Thu Mar 16 2023 01:27:17 GMT+0800 (China Standard Time)

thanks @jakthom and yes @taborwells mentioned about it. thanks again

Sachin Gade · Answer 4 · Thu Mar 16 2023 01:45:54 GMT+0800 (China Standard Time)

:~$ docker pull ghcr.io/silverton-io/buz:v0.13.2 v0.13.2: Pulling from silverton-io/buz Digest: sha256:bcfdb8717a50c057dd8b0098c177faf48dd55b94885c86972360d6dac81d6f0e Status: Image is up to date for ghcr.io/silverton-io/buz:v0.13.2 ghcr.io/silverton-io/buz:v0.13.2 :~$ docker run -it ghcr.io/silverton-io/buz:v0.13.2 docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./buz": stat ./buz: no such file or directory: unknown. ERRO[0000] error waiting for container: :~$

This issue is still persist with new docker version as well @jakthom