Vaultwarden on Synology not working after upgrade

Third Party Help
1

Hi.
I’ve used the Container Manager to upgrade my vaultwarden installation. After the upgrade process was completed, it did not start and this is the error message:

Start container vaultwarden-server1 failed: {"message":"failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: \"/usr/bin/dumb-init\": stat /usr/bin/dumb-init: no such file or directory: unknown"}.

I’ve noticed that there is no project anymore in the Container Manager - I’ve never paid attention to this, but I guess this is what’s gone missing.
I’ve tried to set it up anew (create), but it’s failing when I complete the wizard with this error:

Local port 5151 conflicts with other ports used by other services.

I went into the CLI of my NAS and with netstat I searched for any service listening on port 5151 - nothing found.
This is how it looks like:

image
image740×582 10.3 KB

image
image738×582 9.78 KB

And this is the reverse proxy config:
image
image599×565 16.3 KB

Where am I doing wrong?
Thanks in advance for your help!
F.

2

If you still have dumb-init in there you were using a very old version.

But basically your problem is the same as described here

3

Hi.
I don’t know which version I was running, but it was for sure at least 1.5 years old.
As I’m very noob in all this: what (and how) should I now do, to correct the issue?
I’m not using Portainer.
I somehow understand that I need to remove something from the configuration - but I don’t know where/what.
Thanks for your help!
F.

4

Please read or find the documentation of the tool you are using. Most of us won’t be familiar with it either…

And if you can’t figure it out: maybe you can recreate the setup from scratch with the same /data folder?

5

mmmhhh… the “tool” is actually the Container Manager from Synology…
Anyway: recreating the setup sounds good.
As long as I don’t remove or do anything with the /data folder, I’m safe not losing anything - correct?

Should I also first export everything from one of my Bitwarden clients - just to be “double-safe”?

6

OK - I somehow solved it.
I’ve deleted the old container and installed vaultwarden/server-latest again from scratch.
Now it works.
I was starting to follow instructions found here: Synology: Install Vaultwarden With Portainer – Marius Hosting
Do you suggest to use Portainer, or can I just remove it and continue using Synology’s Container Manager?

7

I am using the default Synology Container Manager, and no problems.

This is the setup I have for the Container Manager > Container:

{
   "CapAdd" : null,
   "CapDrop" : null,
   "cmd" : "/start.sh",
   "cpu_priority" : 50,
   "enable_publish_all_ports" : false,
   "enable_restart_policy" : true,
   "enabled" : true,
   "env_variables" : [
      {
         "key" : "PATH",
         "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
      },
      {
         "key" : "ROCKET_PROFILE",
         "value" : "release"
      },
      {
         "key" : "ROCKET_ADDRESS",
         "value" : "0.0.0.0"
      },
      {
         "key" : "ROCKET_PORT",
         "value" : "80"
      },
      {
         "key" : "DEBIAN_FRONTEND",
         "value" : "noninteractive"
      },
      {
         "key" : "SEND_PURGE_SCHEDULE",
         "value" : "0 0 5 31 2 ?"
      },
      {
         "key" : "TRASH_PURGE_SCHEDULE",
         "value" : "0 0 5 31 2 ?"
      },
      {
         "key" : "SMTP_PASSWORD",
         "value" : "EDIT_HERE_your_smtp_password"
      }
   ],
   "exporting" : false,
   "id" : "EDIT_HERE__docker_id_some_hash_",
   "image" : "vaultwarden/server:latest",
   "is_ddsm" : false,
   "is_package" : false,
   "labels" : {
      "org.opencontainers.image.created" : "2023-11-05T23:08:37+00:00",
      "org.opencontainers.image.description" : "Unofficial Bitwarden compatible server written in Rust - 1.30.0",
      "org.opencontainers.image.documentation" : "https://github.com/dani-garcia/vaultwarden/wiki",
      "org.opencontainers.image.licenses" : "AGPL-3.0-only",
      "org.opencontainers.image.revision" : "EDIT_HERE_some_hash_super_long",
      "org.opencontainers.image.source" : "https://github.com/dani-garcia/vaultwarden",
      "org.opencontainers.image.url" : "https://github.com/dani-garcia/vaultwarden",
      "org.opencontainers.image.version" : "1.30.0"
   },
   "links" : [],
   "memory_limit" : 0,
   "name" : "vaultwarden",
   "network" : [
      {
         "driver" : "bridge",
         "name" : "bridge"
      }
   ],
   "network_mode" : "bridge",
   "port_bindings" : [
      {
         "container_port" : 80,
         "host_port" : 8083,
         "type" : "tcp"
      }
   ],
   "privileged" : false,
   "shortcut" : {
      "enable_shortcut" : false,
      "enable_status_page" : false,
      "enable_web_page" : false,
      "web_page_url" : ""
   },
   "use_host_network" : false,
   "version" : 2,
   "volume_bindings" : [
      {
         "host_volume_file" : "EDIT_HERE_/where_are_you_storing_the_files_and_data_base_at_your_nas/vaultwarden",
         "is_directory" : true,
         "mount_point" : "/data",
         "type" : "rw"
      }
   ]
}

Notice the EDIT_HERE_ for adding your personal information.

Here is my setup at Control Panel > Login Portal > Advanced > Reverse Proxy:

image
image623×580 21 KB

Nothing set on Web Station.

And check your firewall, at Control Panel > Security > Firewall > Edit Rules.
Check if the ports of Vaultwarden network are open.

image
image848×627 24.4 KB

Check which ports are being used from:

image
image1246×665 106 KB

8

I have a similar problem on my Synology after upgrading vaultWarden from 1.2.1 to the latest version.

Start container vaultwarden-server failed: {"message":"failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: \"/usr/bin/dumb-init\": stat /usr/bin/dumb-init: no such file or directory: unknown"}.

Question : how do you edit this setup ?

I found the setup in file: Bitwarden.syno.json

PS: before using vaultwarden, Bitwarden was installed, I change the container on may 21 with same configuration files.

May be it should be good to rebuild my vaultwarden-server from scratch and import a json backup of my passwords. What do you think of that ? (I am still a little bit scared to loose all my data)

{
   "cap_add" : null,
   "cap_drop" : null,
   "cmd" : "/vaultwarden",
   "cpu_priority" : 50,
   "devices" : null,
   "enable_publish_all_ports" : false,
   "enable_restart_policy" : true,
   "enabled" : false,
   "env_variables" : [
      {
         "key" : "SIGNUPS_ALLOWED",
         "value" : "true"
      },
      {
         "key" : "PATH",
         "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
      },
      {
         "key" : "ROCKET_ENV",
         "value" : "staging"
      },
      {
         "key" : "ROCKET_PORT",
         "value" : "80"
      },
      {
         "key" : "ROCKET_WORKERS",
         "value" : "10"
      }
   ],
   "exporting" : false,
   "id" : "0ef3abf0829084aadadfa2e5341f824cb8af060d83068212f0036a47350da977",
   "image" : "vaultwarden/server:latest",
   "is_ddsm" : false,
   "is_package" : false,
   "links" : [],
   "memory_limit" : 157286400,
   "memory_limit_slider" : 100,
   "name" : "bitwarden",
   "network" : [
      {
         "driver" : "bridge",
         "name" : "bridge"
      }
   ],
   "network_mode" : "bridge",
   "port_bindings" : [
      {
         "container_port" : 3012,
         "host_port" : 2166,
         "type" : "tcp"
      },
      {
         "container_port" : 80,
         "host_port" : 2167,
         "type" : "tcp"
      }
   ],
   "privileged" : false,
   "shortcut" : {
      "enable_shortcut" : false
   },
   "use_host_network" : false,
   "volume_bindings" : [
      {
         "host_volume_file" : "/docker/bitwarden",
         "mount_point" : "/data",
         "type" : "rw"
      }
   ]
}
10

You need to make sure the entrypoint isn’t overridden by the tool you use to manage the containers.

That entrypoint isn’t there anymore for a long time already.

11

This is on Synology and I am using Container Manager. To avoid erasing my datas, I have created a specific folder for the new container and I plan to import the vault from a json backup of original container created a few days ago.

Proceeding like this, Is it possible to loose everything ?

12

You can try as many things as you want. Just make a backup of all the files inside "host_volume_file" : "/docker/bitwarden" and export the container .json from the Container Manager.

Maybe, is better if you rebuild the Vaultwarden container.
Take a look at Using Docker Compose · dani-garcia/vaultwarden Wiki · GitHub

13

where is host_volume_file ?

14

Sorry, what I mean, is for you to backup all the files that you have under /docker/bitwarden or wherever you have the Vaultwarden files. Those files should be on your Synology NAS.

15

Do as I did: just remove the old vaultwarden container and install the new one. Point to the same directory/path where your database is actually located and you’re good to go.
This is what I did.
F.

2 Likes
16

I just press action reinit
And it starts

17

I’ve actually tried it, and it worked for me, too. Thanks a lot for sharing this method!

1 Like