In T4249#118633, @Viacheslav wrote:You can get access to host netwoks with set container name foo allow-host-networks
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Mar 16 2025
Mar 16 2025
Mar 11 2025
Mar 11 2025
Mar 10 2024
Mar 10 2024
Jul 12 2023
Jul 12 2023
Feb 26 2023
Feb 26 2023
Feb 16 2022
Feb 16 2022
Apr 27 2021
Apr 27 2021
To reproduce the bug, we need to add a source nat rule first.
configure set nat source rule 100 outbound-interface 'eth0' set nat source rule 100 source address '192.168.0.0/24' set nat source rule 100 translation address masquerade commit save exit
Then if we try to list the nat tables with iptables iptables -t nat -L, we will get error like table 'nat' is incompatible, use 'nft' tool.
Next, if we use podman to create a container sudo podman run -d ubuntu:latest, podman will return the error because it will look up nat rules with iptables.
Apr 26 2021
Apr 26 2021