starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #531] Can't even start container #337

New issue

Closed

opened 2026-03-03 01:28:08 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 01:28:08 +03:00

Owner

Originally created by @bapesta786 on GitHub (Jul 15, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/531

Hey - running docker on Ubuntu Server and I have multiple containers running perfectly fine so far (Radarr, Sonarr, SABNZBD, Guacamole, Portainer) however whenever I try to start Bitwarden, I'm presented with the following error:

docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:275: applying cgroup configuration for process caused "mountpoint for cgroup not found"": unknown.

I'm really not sure what this refers to? I'm using the basic docker run command as stated in the instructions. I've tried different paths, different port numbers etc, but issue persists.

Originally created by @bapesta786 on GitHub (Jul 15, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/531 Hey - running docker on Ubuntu Server and I have multiple containers running perfectly fine so far (Radarr, Sonarr, SABNZBD, Guacamole, Portainer) however whenever I try to start Bitwarden, I'm presented with the following error: docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:275: applying cgroup configuration for process caused \"mountpoint for cgroup not found\"": unknown. I'm really not sure what this refers to? I'm using the basic docker run command as stated in the instructions. I've tried different paths, different port numbers etc, but issue persists.

kerem closed this issue

2026-03-03 01:28:08 +03:00

kerem commented

2026-03-03 01:28:09 +03:00

Author

Owner

@mprasil commented on GitHub (Jul 15, 2019):

Which image are you using?

@mprasil commented on GitHub (Jul 15, 2019): Which image are you using?

kerem commented

2026-03-03 01:28:09 +03:00

Author

Owner

@bapesta786 commented on GitHub (Jul 15, 2019):

Which image are you using?

The one from here:
https://github.com/dani-garcia/bitwarden_rs

docker image list shows:
bitwardenrs/server latest 68d7cf982a87 4 days ago 139MB

@bapesta786 commented on GitHub (Jul 15, 2019): > Which image are you using? The one from here: https://github.com/dani-garcia/bitwarden_rs `docker image list` shows: bitwardenrs/server latest 68d7cf982a87 4 days ago 139MB

kerem commented

2026-03-03 01:28:09 +03:00

Author

Owner

@JasperZ commented on GitHub (Jul 15, 2019):

bitwarden/setup is the official bitwarden image and not the one suitable for this repository. The image for this repo is bitwardenrs/server

@JasperZ commented on GitHub (Jul 15, 2019): [bitwarden/setup](https://hub.docker.com/r/bitwarden/setup) is the official bitwarden image and not the one suitable for this repository. The image for this repo is [bitwardenrs/server](https://hub.docker.com/r/bitwardenrs/server)

kerem commented

2026-03-03 01:28:09 +03:00

Author

Owner

@bapesta786 commented on GitHub (Jul 15, 2019):

bitwarden/setup is the official bitwarden image and not the one suitable for this repository. The image for this repo is bitwardenrs/server

my apologies, i posted the wrong one. My comment has been updated with the correct image.

@bapesta786 commented on GitHub (Jul 15, 2019): > [bitwarden/setup](https://hub.docker.com/r/bitwarden/setup) is the official bitwarden image and not the one suitable for this repository. The image for this repo is [bitwardenrs/server](https://hub.docker.com/r/bitwardenrs/server) my apologies, i posted the wrong one. My comment has been updated with the correct image.

kerem commented

2026-03-03 01:28:09 +03:00

Author

Owner

@bapesta786 commented on GitHub (Jul 15, 2019):

Looks like I have a wider issue - I've restarted a running container (Sabnzbd) and I've been hit with the same message. I will try a restart of the OS and report back.

@bapesta786 commented on GitHub (Jul 15, 2019): Looks like I have a wider issue - I've restarted a running container (Sabnzbd) and I've been hit with the same message. I will try a restart of the OS and report back.

kerem commented

2026-03-03 01:28:09 +03:00

Author

Owner

@bapesta786 commented on GitHub (Jul 15, 2019):

This can be closed - an OS reboot has fixed it .

@bapesta786 commented on GitHub (Jul 15, 2019): This can be closed - an OS reboot has fixed it .