stat /usr/bin/entry.sh: no such file or directory: unknown'

1

I am updating and when I recreate the docker image running portainer on a Raspberry Pi I get the following error:

‘failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: “/usr/bin/entry.sh”: stat /usr/bin/entry.sh: no such file or directory: unknown’

I tried to remove the Entrypoint by leaving the field blank and selecting Override but the error persists

Any ideas?

2

You should revive the entrypoint fully, not leave it blank.

3

Thank you for your response, I tried by all means to eliminate the Entrypoint and I don’t know if I did it correctly.

From a backup card (so as not to be left without production) I tried to follow the steps indicated on the command line:

1- docker pull vaultwarden/server:latest

2- docker run --volumes-from vaultwarden --name vaultwarden_data busybox true

3- docker stop vaultwarden
4- docker rm vaultwarden

5- docker run -d --volumes-from vaultwarden_data --name vaultwarden -p 80:80 vaultwarden/server:latest

6- docker rm vaultwarden_data

BUT in point 5 it presents the following message:

docker run -d --volumes-from vaultwarden_data --name vaultwarden -p 80:80 vaultwarden/server:latest
76c2e15668e4e755b3385f146d247a203de095d26c3d8df4f986981bb1005729
docker: Error response from daemon: driver failed programming external connectivity on endpoint vaultwarden (c49f1e65a17e55d8ce5e33c16d0a1aeeaf84d7260a47f99841923ccb88e231df): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use.

4

I have solved the same problem by selecting the field “default” to the entrypoint.