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

Please document how to change the network using quadlet's. #717

Open
dougsland opened this issue Feb 6, 2025 · 2 comments
Open

Please document how to change the network using quadlet's. #717

dougsland opened this issue Feb 6, 2025 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation jira

Comments

@dougsland
Copy link
Collaborator

It's different scenario but good to have.

See-Also: #713

@nsednev
Copy link
Collaborator

nsednev commented Feb 18, 2025

After our discassion with @dougsland , adding how this should be implemented as quadlet like realtime.

It should be implemented using realtime but with Network session.

should be Network=host or Network=private
restart qm and that's it
podman restart qm
ip addr show
should help to show the difference
just expose 2 systemcalls that are blocked by default
Should be sched_setaffinity and sched_getaffinity
In realtime, there is no blockage.

@Yarboa
Copy link
Collaborator

Yarboa commented Mar 6, 2025

There is another important data related to that,
For nested container run, there were duplications of podman host and podman qm network subnets.
Which caused to podman qm network to have no routing to the mapped ports
#743

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

No branches or pull requests

3 participants