Failure to start latest image on Synology #1858

New Issue

MrUnknownDE · 2026-04-06T02:29:11+02:00

MrUnknownDE commented

2026-04-06 02:29:11 +02:00

Originally created by @throttlemeister on 12/16/2022

I am getting the following error while trying to start the container using the latest image:

Start container Vaultwarden failed: {"message":"OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/usr/bin/dumb-init": stat /usr/bin/dumb-init: no such file or directory: unknown"}.

Reverting back to the previously used image works just fine and the container starts and application works.

I have tried deleting the image and downloading it again, but same result. I am running on Synology, no LXC containers or other virtualization present.

*Originally created by @throttlemeister on 12/16/2022* I am getting the following error while trying to start the container using the latest image: > Start container Vaultwarden failed: {"message":"OCI runtime create failed: container_linux.go:367: starting container process caused: exec: \"/usr/bin/dumb-init\": stat /usr/bin/dumb-init: no such file or directory: unknown"}. Reverting back to the previously used image works just fine and the container starts and application works. I have tried deleting the image and downloading it again, but same result. I am running on Synology, no LXC containers or other virtualization present.

MrUnknownDE closed this issue

2026-04-06 02:29:11 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1858