Protected data will be unavailable when container is destroyed.

[GieltjE]

Steps To Reproduce

1: install the docker container, docker compose up
2: restart using the docker run command
3: view notifications.log

Expected Result

No scary warnings ;)

Actual Result

2023-01-01 12:50:57.676 +00:00 [WRN] No XML encryptor configured. Key {367c96aa-a754-4d6f-a48f-fdbb67418384} may be persisted to storage in unencrypted form.
2023-01-01 12:52:02.709 +00:00 [WRN] Storing keys in a directory '/home/bitwarden/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
2023-01-01 12:53:22.014 +00:00 [WRN] Storing keys in a directory '/home/bitwarden/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.

Data seems to persist just fine, just ugly messages I guess

Screenshots or Videos

No response

Additional Context

No response

Githash Version

455d62e-dirty

Environment Details

• OS: Win 11 insider
• Env: Docker
• Hardware: 3700X 64GB ram

Database Image

Mariadb: 10.10.2

Issue-Link

#2480

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[justindbaur]

@GieltjE Sorry for the super late resolution but I'm going to close this as won't fix. Persistent data protection is not required for the notifications service. We do persist the keys for the other services when it's necessary but that isn't the case for this one. The warning comes from within ASP.NET Core, and I don't believe it's worth the effort to suppress it. I'm also quite sure the standard deployment would be subject to the same warning.