mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #694] DOCKER: failed to start containers: bitwarden #469
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#469
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @liangxyz on GitHub (Nov 1, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/694
hello ,I found that the bitwarden_rs cant run in my vps
when I use command line :docker start bitwarden .it have an error
Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \"bitwardenrs/server:latest\": stat bitwardenrs/server:latest: no such file or directory": unknown Error: failed to start containers: bitwardenSo can any body help me ? thank you very much
@BlackDex commented on GitHub (Nov 1, 2019):
Looks like an issue with the command line arguments.
Please check if if it you didn't make a mistake with some of the arguments.
Please double check the wiki: https://github.com/dani-garcia/bitwarden_rs/wiki/Starting-a-Container
@liangxyz commented on GitHub (Nov 1, 2019):
hello,when I use this command :docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:latest ,it returned an error again ,I already run docker stop bitwarden
docker: Error response from daemon: Conflict. The container name "/bitwarden" is already in use by container "93255bc2bec8d1222b9472a349bb3f1fe1f537eab7a7a5d413253d6287954fd4". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'.