Unable to use custom network for container

[Pilchh]

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]

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]

@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]

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: - /mnt/hgfs/Docker/homer:/www/assets user: 1000:1000 # default environment: - INIT_ASSETS=1 # default restart: always mac_address: 02-42-C0-A8-00-45 networks: CMH: ipv4_address: 192.168.0.69