Replies: 6 comments 8 replies
-
|
That is to be expected as pasta uses the same ip address in the netns by default so you are not actually connecting to the host in this case, see |
Beta Was this translation helpful? Give feedback.
-
|
I guess your container has an address in 94.0.0.0/8, correct? By default, with pasta, the new default rootless network backend, your container will inherit IP addresses and routes from one host upstream interface. See #19213 (comment) for a detailed explanation. Can you please have a look with |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
you have to check |
Beta Was this translation helpful? Give feedback.
-
Here's all of them: The nextcloud-aio bridge network seems to use podman2: |
Beta Was this translation helpful? Give feedback.
-
|
So this still doesn't tell me why I can connect with the host on 192.168.1.1 (br0) and not the interface with my public ip 94.x.x.x (ens6f0.300). |
Beta Was this translation helpful? Give feedback.
-
|
Because this is associated to your first default route (for IPv4) on the host, I guess. From |
Beta Was this translation helpful? Give feedback.
-
|
That it correct, it's my internet connection and the default gateway to the outside world. |
Beta Was this translation helpful? Give feedback.
-
Right, so that from that network namespace, you have no NAT, because the internal address is the same as the external address. It's generally a neat feature but it can be a bit annoying if you're not used to it, I realise.
Note that pasta is just copying that one, the rest are interfaces to connect your containers in the same pod/namespace.
Worse, they'll lose their address. They need an address. What you can do is to specify another address for the namespace -- I don't remember right now how that's done but I'm fairly sure it's documented somewhere. |
Beta Was this translation helpful? Give feedback.
-
|
Al right, thanks for all of the clarification and explanation. |
Beta Was this translation helpful? Give feedback.
-
|
This: #22653 (comment) is what I meant: pass another address directly to pasta, if you want/need. |
Beta Was this translation helpful? Give feedback.
-
|
So to give a little bit more background info, I'm running nextcloud-aio which comes with a so called "master" container. Now I've tried to work around this by adding this to the master container: But it seems the master container will not pass on the "add-host" field to its child containers so the above workaround only applies to the master container. As a last resort I simply edited the /etc/hosts file on my hosts so it applies system-wide. |
Beta Was this translation helpful? Give feedback.
-
I'm running podman 5.0.3 on Fedora 40 (x86-64).
On my host I have a webserver (nginx) running which listens on port 80 and 443 on all interfaces.
I have two main interfaces:
br0: 192.168.1.1 (firewalld zone "internal")
ens6f0.300: 94.x.x.x (firewalld zone "external")
Both firewalld zones have port 80tcp and 443tcp open.
So doing a curl on the host works for both http://192.168.1.1 and http://94.x.x.x
This changes when I try it inside my nextcloud rootless container.
Only http://192.168.1.1 seems to work.
Very strange that from within the container only 192.168.1.1 seems to work.
podman system info:
podman network inspect nextcloud-aio:
podman container inspect nextcloud-aio-nextcloud:
I can't figure out why the rootless container is only capable of connecting with 192.168.1.1 and not with my public ip, while both of these interfaces live on the same host.
Any help would be greatly appreciated :)
Beta Was this translation helpful? Give feedback.
All reactions