Problem on docker run #3517

Closed
opened 2026-04-06 04:56:56 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @MarkOnDuty on 3/5/2019

My suspicion is the problem is with Docker or LXC/LXD, but I'll start here.

I'm trying to get a bitwarden_rs server up and running. Created a new LXD container, hopped into it, and did the following:

apt update
apt upgrade
curl -sSL https://get.docker.com | sh
mkdir /bw-data
docker pull mprasil/bitwarden:latest
docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 mprasil/bitwarden:latest

No issues with all but the last command. Here's the result of the run:

d6423f3b25b35a18a530b4ea2629f745460d94b64e2b554d65653661f4f819e7
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"proc\\\" to rootfs \\\"/var/lib/docker/vfs/dir/428b63304ee65c84c9962aa1d6df8d919a7f931ba914ed73963af3ee416951d0\\\" at \\\"/proc\\\" caused \\\"permission denied\\\"\"": unknown.

Any ideas? Or should I move up the chain and ask the Docker or LXC/LXD people?

*Originally created by @MarkOnDuty on 3/5/2019* My suspicion is the problem is with Docker or LXC/LXD, but I'll start here. I'm trying to get a bitwarden_rs server up and running. Created a new LXD container, hopped into it, and did the following: ``` apt update apt upgrade curl -sSL https://get.docker.com | sh mkdir /bw-data docker pull mprasil/bitwarden:latest docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 mprasil/bitwarden:latest ``` No issues with all but the last command. Here's the result of the run: ``` d6423f3b25b35a18a530b4ea2629f745460d94b64e2b554d65653661f4f819e7 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"proc\\\" to rootfs \\\"/var/lib/docker/vfs/dir/428b63304ee65c84c9962aa1d6df8d919a7f931ba914ed73963af3ee416951d0\\\" at \\\"/proc\\\" caused \\\"permission denied\\\"\"": unknown. ``` Any ideas? Or should I move up the chain and ask the Docker or LXC/LXD people?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#3517