Clarify network configuration when using podman machine #2402
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: chrw The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Christian Wolff <[email protected]>
chrw
force-pushed
the
update_containersconf_doc
branch
from
07a5a84 to
bcb7be7
Compare
| Note: If Podman is running in a virtual machine using `podman machine` (this | ||
| includes Mac and Windows hosts), ensure that you add the configuration in the | ||
| virtual machine by using `podman machine ssh`. |
There was a problem hiding this comment.
Note this does not only effect network settings, almost all option from this file must be set server side (in the machine). Notable exceptions are [machine], [farms], [engine.service_destinations], compose_providers, compose_warning_logs, and the remote option and likely more we don't even know about.
So I think this should likely be reworded and put as part of the main description. (Overall we as a team are currently trying to figure out how this whole situation can be improved)
There was a problem hiding this comment.
I'm not sure how to rephrase this to ensure that the information isn't overlooked. My thought was that including such a note directly within the configuration type would make sense.
There was a problem hiding this comment.
How should we move forward with this change?
Fixes: containers/podman#25763
Avoid confusion with the
networkconfiguration usingpodman machine.