#Pi.Hole and Bitwarden on same Raspberry Pi

13 messages · Page 1 of 1 (latest)

green valve
#

I was hoping someone here can advise. I have pi.hole running on a raspberry pi 4, 4gb, Bullseye 64 bit. Can I also run Bitwarden? How? Inside Docker?

It was installed on a fresh install of Bullseye.

gritty canyon
#

I'm not 100% sure, but if you're able to install Docker, it's easy to install bitwarden indeed

rich oyster
#

Personally I'd put both Pi Hole and Bitwarden in Docker containers. I realise that might mean another fresh install 😂

#

But having all your services in containers makes maintenance super easy and consistent

gritty canyon
#

Agreed!

tardy depot
#

there'll be another container on the list then, duplicati, great backup solution

green valve
#

Yes. I've not ever used docker yet. This seems a good opportunity to learn.

tardy depot
#

portainer should be on your list, makes docker mgmt in a browser a doddle

rich oyster
#

Honestly I used to use Portainer but I don't anymore. I found it had some annoying traits. Like when updating a container image it won't remember which environment variables you originally explicitly set on the container, so it tries to apply all of the environment variables from the old container to the new one. I've found several times that that can break the updated container. It also needs access to docker.sock, which is basically equivalent to giving it root access on the host, so you'd better trust it! All in all I found it more convenient to ditch it, in the end, and just keep a set of tiny shell scripts that contain the launch command for each of my containers.

little tiger
#

You should be able to load docker alongside the native PiHole Raspbian build and run it there.
Mine (Pi2 1Gb) without docker only uses about 1-3%CPU and 200Mb RAM, so you should have plenty of overhead for containers.

#

For reference, a (2nd) PiHole I have running in a NAS docker container only uses 50Mb RAM and 0.02% CPU.

The RPi is our primary and the NAS the secondary for the LAN and WAN.

While you're installing BitWarden, it's worth installing Tailscale on it too, so you can have DNS sinkhole while using mobile data 🙂

green valve
#

OK. I did it. But I didn't use pi.hole. I couldn't figure out how to put it inside a container. I used Adguard instead. Then Portainer, and Vaultwarden, but I'm now considering what @rich oyster said. Before starting this, I had no idea what I was doing. Still don't, but I have it up and working. Now I have to be sure I don't give all my passwords away.

After I installed Vaultwarden, I couldn't create an account because I couldn't access the admin page via SSL.

I created a Cloudflare tunnel and installed the cloudflare service in the root of the Pi. I followed a video using the directions from the Cloudflare website. Unfortunately, the container instructions wouldn't work.

Now I can access vaultwarden from my own domain. Today, I'll add tunnels to the Adguard and Portainer admin.

QUESTIONS: Should I worry that the Cloudflare service isn't in a container? Now that it is working, is there a way to move it into a container?

I'm also going to look into setting up firewall fuels to accept connections only from my phone, tablet, and computer.

tardy depot