Broken OCI Proxmox unprivileged deployment?

[bradyjoh]

Self-host installation scripts issue

• I understand this repository only tracks self-host installation scripts and any other issues should be reported in bitwarden/server

Steps To Reproduce

• Proxmox 9.1 with OCI support
• Go to node/storage/CT Templates
• Pull from OCI Registry, paste ghcr.io/bitwarden/lite and pick latest and download
• Create CT based on template
• Add environment variables needed for function (see my link below for what I input)
• Add mountpoint to preserve /etc/bitwarden
• Start
• Enter container with pct enter <id> from the Proxmox shell
• Check nginx log /var/log/nginx/error.log and see 2026/03/19 12:38:52 [emerg] 142#142: open() "/var/run/nginx/nginx.pid" failed (2: No such file or directory)

Expected Result

No errors. Web UI accessible

Actual Result

Error with the nginx pid file, which I assume is causing issues reaching the UI. I try to go to https://ipaddress:8443 and get a connection refused error

Screenshots or Videos

No response

Additional Context

#358 (comment)

Build Version

latest as of 3/18

Environment

Self-Hosted

Environment Details

No response

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.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-33883
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-33883

[bradyjoh]

I'm not sure if this is a user error, or an issue with Proxmox specifically, or maybe something with root permissions, but I wanted to share any information I can so I can get this running. I've been using the full version of Bitwarden for a few years self-hosted, and am looking to migrate to the Lite version to save on CPU/RAM for the two user + 1 organization environment I manage

[NovaSilentium]

Hi there,

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!