search

bastienwirtz / homer

A very simple static homepage for your server.
https://homer-demo.netlify.app/
Apache License 2.0
9.13k stars 774 forks source link

Unable to use custom network for container #453

Open Pilchh opened 2 years ago

Pilchh commented 2 years ago

Hi, I'm trying to use a custom macvlan docker network to give the homer container a local IP address for use with pihole DNS. Whenever I change the homer containers network from bridge to my custom network, I can not access homer from the new IP address. I have used the same network on other containers and it works fine. Not really sure why it's not working.

Let me know what you think.

Thanks :)

bastienwirtz commented 2 years ago

Hello @Pilchh,

That's a good question, I never used macvlan networks. Homer's dockerfile is pretty simple, I don't see anything that could explain the difference with other containers :thinking:

Maybe share a configuration exemple ?

FriendlyNGeeks commented 1 year ago

@Pilchh do you have a screen shot of the console log when trying to reach Homer via HTTP (error 404) also do you have your docker compose for Homer ports?

cmh716 commented 1 year ago

I have no problem accessing homer that's on macvlan. My problem is that homer gets CORS errors for every service I try to monitor because every deployed docker container has a unique ip address (using macvlan).

homer: image: b4bz/homer container_name: homer volumes: