Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libnetwork: bridge network with umanaged mode should allow existing host subnet #2322

Open
Luap99 opened this issue Feb 13, 2025 · 0 comments

Comments

@Luap99
Copy link
Member

Luap99 commented Feb 13, 2025

In unmanaged mode it is very likely that the subnet that the user chooses is in use on the host as it is assigned the the bridge interface.

# podman network create --interface-name br0 --opt mode=unmanaged --disable-dns --subnet 192.168.122.0/24  unmanaged-br0
Error: subnet 192.168.122.0/24 is already used on the host or by another config

However that is a common use case so we need to allow it, it is then on the user to ensure there will be no ip conflicts in the sunet with other systems on the host, i.e. they likely should reserve a range for podman to use and then specify it with --ip-range so podman only selects ips from there and does not accidentally assign one that is used by other systems on the local LAN.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant