Question How to run Bitwarden via Docker on my NAS?

Currently reading
Question How to run Bitwarden via Docker on my NAS?

Status
Not open for further replies.
I see. I don’t have Docker installed though (in spite Of having 8GB ram now).
Well despite that you have 8GB ram Docker will not take that much hit on your ram as you think. This is not a virtual machine hypervizor and as such doesnt need to run a full blown OS to run a single app on it. The beauty of Docker is that it will use only the amount of resources (cpu and ram) that it needs to run the app it self, rest is shared with the host that Docker is running on.
 
Piggy-backing on Rusty's RAM comment.... I have a 418Play. Here's Docker w/BW (only)...
MWMCMqM.png

RSgdfQx.png


Yea... I should probably pony up for an 8GB RAM chip
 
Well despite that you have 8GB ram Docker will not take that much hit on your ram as you think.

Thanks. I believe my reply was a self reflection on a comment I made on the good old forum when I was asking about upgrading the RAM. I said this will allow me to try things in docker. Unfortunately, time won’t give me time.

But maybe BW and a few other things in my mind (a weather station to monitor a green house is one) will push me to installing it. Undoubtedly, I’ll need some help by then.
 
Regarding the tutorial, why not leave port 3012 mapped to "auto"? Do we interact with that port in anyway? Is it related to BW's emailed invitations?

How does updating work? Is the user notified when an update is available? In my case I believe the image has been updated, but I cannot locate a change log for that update.
 
Regarding the tutorial, why not leave port 3012 mapped to "auto"? Do we interact with that port in anyway? Is it related to BW's emailed invitations?

How does updating work? Is the user notified when an update is available? In my case I believe the image has been updated, but I cannot locate a change log for that update.
We can continue some Q&A in the resource discussion for this topic.
 
How does updating work? Is the user notified when an update is available? In my case I believe the image has been updated, but I cannot locate a change log for that update.
This is a weak spot for Docker in general. There is a number of ways (even docker images) that can make this a smooth solution, but personally, I avoid auto-update to the latest version. Always want to have control over my containers and versions.

microbadger can help you with this, as one solution, but I guess your best bet is to use ouroboros or watchtower. Ouroboros is maybe a bit of a preferred choice but both will work fine. Still, back in the day WT totally messed up some of my containers and since then I stopped using an automatic update mechanism.
 
At the time I posted there was no ability to comment on the tutorial, I see that is now moved to "Resources". Hopefully comments/questions are permitted there.
Yes, we are still adding new stuff to the forum so now we have a Resources page where you can publish a tutorial or comments and review current resources.
 
Locking this thread due to publish tutorial:

Discussion can continue over there.
 
Status
Not open for further replies.

Similar threads

I have no idea what you are doing, but I just tested it based on the instructions of the guide you linked...
Replies
11
Views
2,775
  • Question
It is realy not complicated to translater container arguments to Synology UI settings. Here is what each...
Replies
2
Views
1,880
Same here This worked for me: Task script: #!/bin/bash cd /volume1/docker/[directory where...
Replies
10
Views
5,925
@one-eyed-king , I have tried your first step: sudo synogroup --add docker and encounter the following...
Replies
11
Views
31,060
Done on both my NAS'es running Docker! :) Thanks again!
Replies
9
Views
13,504

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top