[GH-ISSUE #2999] Failure to start latest image on Synology #14228

New Issue

GiteaMirror · 2026-04-23T05:59:13-05:00

GiteaMirror commented

2026-04-23 05:59:13 -05:00

Originally created by @throttlemeister on GitHub (Dec 16, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2999

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 GitHub (Dec 16, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2999 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.

GiteaMirror closed this issue

2026-04-23 05:59:13 -05:00

GiteaMirror commented

2026-04-23 05:59:14 -05:00

@BlackDex commented on GitHub (Dec 16, 2022):

See:

@BlackDex commented on GitHub (Dec 16, 2022): See: - #2826 - #2863 - #2854

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#14228