"agent container running in more than a single Docker network. This might cause communication issues | network_count=2" #9286
Replies: 4 comments
-
Containers should not be connected to the ingress network. Ingress is for routing internal traffic. Containers should be connected to an overlay network. Do you have containers on the ingress network? Thanks! |
Beta Was this translation helpful? Give feedback.
-
For the latter I only have them in an overlay network: If it helps at all, here's my entire networks list. I don't have any containers specifically added to the ingress network: |
Beta Was this translation helpful? Give feedback.
-
Upon further review, I am seeing here you have debug enabled. You can ignore those messages. Thanks! |
Beta Was this translation helpful? Give feedback.
-
The same thing happens to me. This is because port 9001 is published and the service is automatically added to the ingress network. I have the problem that I cannot include the environment in Portainer ( |
Beta Was this translation helpful? Give feedback.
-
Before you start, we need a little bit more information from you:
Use Case (delete as appropriate): Using Portainer at Home, Using Portainer in a Commercial setup. Home
Have you reviewed our technical documentation and knowledge base? Yes
Question:
When looking at the Portainer Agent log, it shows the line in the title; what does this mean exactly? In my Compose I only see 1 network?
Also the line:
skipping invalid container network | ingress=true network_name=ingress scope=swarm
Why is that invalid?
Log:
Compose:
Beta Was this translation helpful? Give feedback.
All reactions