Permission denied: '/home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der' #211

New Issue

Closed

opened 2026-02-04 18:38:43 +03:00 by OVERLORD · 4 comments

OVERLORD commented 2026-02-04 18:38:43 +03:00

Owner

Copy Link

Originally created by @LukasWerfel on GitHub (Jan 25, 2019).

All of the sudden bitwarden cannot be upped anymore.

[user]$ docker-compose up -d
Building standardnotes
Traceback (most recent call last):
  File "site-packages/docker/utils/build.py", line 96, in create_archive
PermissionError: [Errno 13] Permission denied: '/home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "bin/docker-compose", line 6, in <module>
  File "compose/cli/main.py", line 71, in main
  File "compose/cli/main.py", line 127, in perform_command
  File "compose/cli/main.py", line 1080, in up
  File "compose/cli/main.py", line 1076, in up
  File "compose/project.py", line 475, in up
  File "compose/service.py", line 358, in ensure_image_exists
  File "compose/service.py", line 1082, in build
  File "site-packages/docker/api/build.py", line 154, in build
  File "site-packages/docker/utils/build.py", line 31, in tar
  File "site-packages/docker/utils/build.py", line 100, in create_archive
OSError: Can not read file in context: /home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der
[23602] Failed to execute script docker-compose
[user@localhost server]$ SUDO ^C
[user@localhost server]$ sudo systemctl restart docker
[user@localhost server]$ docker-compose up -d
Building standardnotes
Traceback (most recent call last):
  File "site-packages/docker/utils/build.py", line 96, in create_archive
PermissionError: [Errno 13] Permission denied: '/home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "bin/docker-compose", line 6, in <module>
  File "compose/cli/main.py", line 71, in main
  File "compose/cli/main.py", line 127, in perform_command
  File "compose/cli/main.py", line 1080, in up
  File "compose/cli/main.py", line 1076, in up
  File "compose/project.py", line 475, in up
  File "compose/service.py", line 358, in ensure_image_exists
  File "compose/service.py", line 1082, in build
  File "site-packages/docker/api/build.py", line 154, in build
  File "site-packages/docker/utils/build.py", line 31, in tar
  File "site-packages/docker/utils/build.py", line 100, in create_archive
OSError: Can not read file in context: /home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der
[23789] Failed to execute script docker-compose

My compose file

Problem remains after using a backuped volume that previously worked.

Originally created by @LukasWerfel on GitHub (Jan 25, 2019). All of the sudden bitwarden cannot be upped anymore. ``` [user]$ docker-compose up -d Building standardnotes Traceback (most recent call last): File "site-packages/docker/utils/build.py", line 96, in create_archive PermissionError: [Errno 13] Permission denied: '/home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "bin/docker-compose", line 6, in <module> File "compose/cli/main.py", line 71, in main File "compose/cli/main.py", line 127, in perform_command File "compose/cli/main.py", line 1080, in up File "compose/cli/main.py", line 1076, in up File "compose/project.py", line 475, in up File "compose/service.py", line 358, in ensure_image_exists File "compose/service.py", line 1082, in build File "site-packages/docker/api/build.py", line 154, in build File "site-packages/docker/utils/build.py", line 31, in tar File "site-packages/docker/utils/build.py", line 100, in create_archive OSError: Can not read file in context: /home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der [23602] Failed to execute script docker-compose [user@localhost server]$ SUDO ^C [user@localhost server]$ sudo systemctl restart docker [user@localhost server]$ docker-compose up -d Building standardnotes Traceback (most recent call last): File "site-packages/docker/utils/build.py", line 96, in create_archive PermissionError: [Errno 13] Permission denied: '/home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "bin/docker-compose", line 6, in <module> File "compose/cli/main.py", line 71, in main File "compose/cli/main.py", line 127, in perform_command File "compose/cli/main.py", line 1080, in up File "compose/cli/main.py", line 1076, in up File "compose/project.py", line 475, in up File "compose/service.py", line 358, in ensure_image_exists File "compose/service.py", line 1082, in build File "site-packages/docker/api/build.py", line 154, in build File "site-packages/docker/utils/build.py", line 31, in tar File "site-packages/docker/utils/build.py", line 100, in create_archive OSError: Can not read file in context: /home/user/server-setup/server/volumes/bitwarden/data/rsa_key.der [23789] Failed to execute script docker-compose ``` [My compose file](https://github.com/LukasWerfel/server-setup/blob/master/server/docker-compose.yml) Problem remains after using a backuped volume that previously worked.

OVERLORD closed this issue 2026-02-04 18:38:47 +03:00

OVERLORD commented 2026-02-04 18:38:56 +03:00

Author

Owner

Copy Link

@dani-garcia commented on GitHub (Jan 26, 2019):

There hasn't been any change to that recently, so I'm not sure why it would break now.

Can you check the permission of that file, to see if you can access it correctly?

You could also try deleting all the rsa_key.* files, they'll be regenerated at next start, but you'll have to login again with all the clients.

@dani-garcia commented on GitHub (Jan 26, 2019): There hasn't been any change to that recently, so I'm not sure why it would break now. Can you check the permission of that file, to see if you can access it correctly? You could also try deleting all the rsa_key.* files, they'll be regenerated at next start, but you'll have to login again with all the clients.

OVERLORD commented 2026-02-04 18:39:26 +03:00

Author

Owner

Copy Link

@LukasWerfel commented on GitHub (Jan 26, 2019):

Hi, turns out it was not a bitwarden specific issue, thanks for your help!

@LukasWerfel commented on GitHub (Jan 26, 2019): Hi, turns out it was not a bitwarden specific issue, thanks for your help!

OVERLORD commented 2026-02-04 18:39:36 +03:00

Author

Owner

Copy Link

@jonahbron commented on GitHub (Oct 31, 2020):

@LukasWerfel What was the solution for you? I'm having this same error, but no matter how much I open up the permissions, I still get the error.

@jonahbron commented on GitHub (Oct 31, 2020): @LukasWerfel What was the solution for you? I'm having this same error, but no matter how much I open up the permissions, I still get the error.

OVERLORD commented 2026-02-04 18:39:43 +03:00

Author

Owner

Copy Link

@jonahbron commented on GitHub (Oct 31, 2020):

Found the issue. I wasn't taking into account the ReadWritePaths set in my systemd service. Once I moved my data dir into that path it worked fine.

@jonahbron commented on GitHub (Oct 31, 2020): Found the issue. I wasn't taking into account the `ReadWritePaths` set in my systemd service. Once I moved my data dir into that path it worked fine.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear 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

Mirrored from GitHub Pull Request

question

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#211