JorgeB Posted June 13 Share Posted June 13 That looks like a macvlan call trace, try switching to ipvlan. 1 Quote Link to comment
062bel313 Posted June 14 Author Share Posted June 14 20 hours ago, JorgeB said: That looks like a macvlan call trace, try switching to ipvlan. Oh looks like that was the issue. No more traces in the logs 😀. I switched to ipvlan, but now when I reboot the docker all my dockers that uses custom network with static IP are not starting. I get this error  These are the settings I have in the docker networks  I deleted the custom network and recreated again, but getting same issue during the docker start. Anything I am doing wrong?  Thank you, Quote Link to comment
JorgeB Posted June 14 Share Posted June 14 I would think that ipvlan should work the same, but you can try macvlan with bridging disabled, that also resolves the call traces: Â https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces Quote Link to comment
062bel313 Posted June 17 Author Share Posted June 17 (edited) Even with the macvlan, bridging disabled, I am getting the network not found error. switching either to ipvan or macvlan doesn't start up the custom network. All my dockers are custom, all start fine, except the one that are external are not starting up.   I think I have all the settings correct.  And this is the docker:  my custom networks:  sample of my docker compose in Portainer: services:  homeassistant:   container_name: homeassistant   image: "ghcr.io/home-assistant/home-assistant:stable"   labels:    - net.unraid.docker.icon=https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/homeassistant-logo.png    - net.unraid.docker.webui=http://192.168.5.100:8123   volumes:    - /mnt/user/appdata/home_assistant/config:/config    - /etc/localtime:/etc/localtime:ro    - /run/dbus:/run/dbus:ro   restart: always   networks:    eth0:     ipv4_address: 192.168.5.100   ports:    - 8123:8123 networks:   eth0:     external: true  May be I am doing something wrong. Diagnostics also attached if it helps. unraid-diagnostics-20240617-1301.zip  Edited June 18 by 062bel313 docker screenshot added Quote Link to comment
062bel313 Posted June 17 Author Share Posted June 17 I think I might have found the issue, but I am not sure how to resolve it. Everytime I do enable/disable docker it doesn't preserve my network, with macvlan as well as ipvlan. Â Â Now the id is different, even though I have preserve user defined networks enabled. Am I doing anything wrong? Â Quote Link to comment
JorgeB Posted June 18 Share Posted June 18 I would suggest recreating the docker image and all custom networks: Â https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Then: https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks Quote Link to comment
062bel313 Posted June 18 Author Share Posted June 18 Before recreating the docker image, I wanted to try to create a different network with parent as br0 (for ipvlan) in one container and use it in other containers. With this configuration it works somehow. If I enable/disable the docker everythig start now.  Created main network from pihole container and used the same network in other container as below.  pihole: networks: vlan_network: ipv4_address: 192.168.5.110 networks: vlan_network: driver: ipvlan driver_opts: parent: br0 ipam: driver: default config: - subnet: 192.168.5.0/24 ip_range: 192.168.5.0/25 gateway: 192.168.5.1  and other networks: networks: pihole_vlan_network: ipv4_address: 192.168.5.100 networks: pihole_vlan_network: external: true   Is this just a fluke or was I doing it wrong before? any insights (to understand).  If this fails, I will recreated= docker image as suggested. Quote Link to comment
JorgeB Posted June 19 Share Posted June 19 9 hours ago, 062bel313 said: Is this just a fluke or was I doing it wrong before? Not sure, networking is not my strong suit, but glad it's working. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.