Bitwarden not started after update TrueNas (24.04 -> 25.10.1)

Apps and Virtualization
1

I have a container (the “/ui/containers” section in TrueNAS) that is based on: Base image: Ubuntu jammy amd64 (20251030_07:42)
With only Bitwarden installed on it.
In TrueNAS 24.04, the container worked without problems, and after upgrading to TrueNAS 25.10.1, Bitwarden stopped running in the container.

Please tell me what could be the error?

On the advice of Google AI, I tried:

  1. Change ports in the config.yml file 80 → 8080, 443 → 8443 - It didn’t help
  2. In TrueNAS system advanced → Sysctl → added the variable SYSCTL net.ipv4.ip_unprivileged_port_start=0 - Did not help

Log error

root@bitwarden:/bitwarden# ./bitwarden.sh rebuild
 _     _ _                         _
| |__ (_) |___      ____ _ _ __ __| | ___ _ __
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \
| |_) | | |_ \ V  V / (_| | | | (_| |  __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_|  \__,_|\___|_| |_|

Open source password management solutions
Copyright 2015-2026, Bitwarden, Inc.
https://bitwarden.com, https://github.com/bitwarden

===================================================

WARNING: This script is running as the root user!
If you are running a standard deployment this script should be running as a dedicated Bitwarden User as per the documentation.
Do you still want to continue? (y/n): y
Continuing....
bitwarden.sh version 2026.1.1
Docker version 29.2.1, build a5c7197
Docker Compose version v5.0.2

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied

Run 'docker run --help' for more information
2

I tried to create a new container, but I got the same error on ./bitwarden.sh install

bitwarden@bitwarden2:/opt/bitwarden$ ./bitwarden.sh install
 _     _ _                         _
| |__ (_) |___      ____ _ _ __ __| | ___ _ __
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \
| |_) | | |_ \ V  V / (_| | | | (_| |  __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_|  \__,_|\___|_| |_|

Open source password management solutions
Copyright 2015-2026, Bitwarden, Inc.
https://bitwarden.com, https://github.com/bitwarden

===================================================

bitwarden.sh version 2026.1.1
Docker version 29.2.1, build a5c7197
Docker Compose version v5.0.2

(!) Enter the domain name for your Bitwarden instance (ex. bitwarden.example.com): 

(!) Enter the database name for your Bitwarden instance (ex. vault): 

2026.1.1: Pulling from bitwarden/setup
df03857d1b60: Pull complete 
630af7e90e7f: Pull complete 
015a666ee15b: Pull complete 
9176769357ba: Pull complete 
f637881d1138: Pull complete 
603e866db035: Pull complete 
2d819ae9c810: Pull complete 
ef8e7f7cef36: Pull complete 
49ab0cb28b1d: Pull complete 
624ec1b4baae: Pull complete 
7cffaed9500a: Pull complete 
Digest: sha256:39d23f0625d8c3efd0ec687d94945922aa84974b0fc9688dbe219e08b17e1d27
Status: Downloaded newer image for ghcr.io/bitwarden/setup:2026.1.1
ghcr.io/bitwarden/setup:2026.1.1
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 3: permission denied

Run 'docker run --help' for more information
3

The easiest and fastest solution was to switch to “Virtual Machines”

4

If this was a VM created in the Containers screen, it was expected behavior and switching it to Virtual Machines was the right move.

https://www.truenas.com/docs/scale/25.10/gettingstarted/versionnotes/#25.10.0

  • VMs created in TrueNAS 25.04 (pre-25.04.2) and displayed on the Containers screen no longer automatically start on system boot to prevent conflicts with VMs on the Virtual Machines screen. See Containers and Virtual Machines for more information.
1 Like