Docker

1448 readers

2 users here now

founded 3 years ago

MODERATORS

erlingur@programming.dev

ProgramPhoenix@programming.dev

Ategon@programming.dev

Using PiHole+Unbound and NextCloud in Docker / Port 80 conflict (feddit.org)

submitted 2 weeks ago by sp3ctre@feddit.org to c/docker@programming.dev

8 comments fedilink hide all child comments

Hey guys!

I want to take the next step in selfhosting and it seems that docker is something I need for my projects.

I am running a Raspberry Pi 5 (16GB) with pihole+unbound and I want to install NextCloud as well. The problem is: NextCloud and PiHole both want to use port 80, which conflicts.

So, I probably need to remap the ports with docker. I already saw some videos and read some instructions, but so far I had no success setting it up. It's pretty confusing, with no docker-experience.

How do you handle this issue? Maybe I just need a little push in the right direction.

~sp3ctre

you are viewing a single comment's thread
view the rest of the comments

[–] HumbleBragger@piefed.social 5 points 2 weeks ago (1 children)

In your compose file, in ports, just set the first number to the port number you wanna use. I use 8088 for my nextcloud for instance. The second number is the number the docker container is set to use internally. So you can just set like 8088:80 in your compose file. That should do the trick.

[–] sp3ctre@feddit.org 1 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

Sounds great!

Can you provide your compose-file? I feel like I need a correct and up-to-date setup to properly understand it.

Is PiHole, Unbound and NextCloud running in the same compose file and are you using different networks in it?

[–] infeeeee@lemmy.zip 1 points 2 weeks ago

I use this community maintained version, they have a very detailed description and an example compose: https://github.com/nextcloud/docker#base-version---apache

[–] HumbleBragger@piefed.social 1 points 2 weeks ago

Actually I don't have unbound and runs directly in my pi2 so I just have a nextcloud in a compose file that's been running for 3 years. But the issue seems to be with docker port mapping. You just have to remember to use different port mapping to the same 80 port they need and you should be good.