-
Notifications
You must be signed in to change notification settings - Fork 46
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
Improvements to the systemd unit file #207
Conversation
/approve LGTM |
When this is installed in /etc/systemd/system/, the very generic unit name/description can be a problem. Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
This will allow to always install gv-user-network.service system-wide. After configuring a tap network device, gv-user-network.service can be enabled/started with: # systemctl enable --now gv-user-network@vsock0 (if the device is named `vsock0`) Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
This ensures that the network device the systemd unit needs exists. Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
gv-user-network@.service can be used with any network device, and is not enabled by default, so we can always install it. Once a tap device is configured (for example using contrib/networkmanager/vsock0.nmconnection), user mode networking can be enabled/started with `systemctl enable --now gv-user-network@vsock0' If the service not explicitly enabled/started, the installed unit file won't do anything. Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
…iner image The service file is based on the upstream one https://github.com/containers/gvisor-tap-vsock/blob/main/contrib/systemd/user-network.service after containers/gvisor-tap-vsock#207 is merged.
LGTM |
Trying to move this forward following Brent's review |
@cfergeau: you cannot LGTM your own PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This aligns the naming with 'gvproxy' and hopefully makes it a bit more descriptive Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
/hold |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: baude, cfergeau The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…iner image The service file is based on the upstream one https://github.com/containers/gvisor-tap-vsock/blob/main/contrib/systemd/user-network.service after containers/gvisor-tap-vsock#207 is merged.
…iner image The service file is based on the upstream one https://github.com/containers/gvisor-tap-vsock/blob/main/contrib/systemd/user-network.service after containers/gvisor-tap-vsock#207 is merged.
…iner image The service file is based on the upstream one https://github.com/containers/gvisor-tap-vsock/blob/main/contrib/systemd/user-network.service after containers/gvisor-tap-vsock#207 is merged.
…iner image The service file is based on the upstream one https://github.com/containers/gvisor-tap-vsock/blob/main/contrib/systemd/user-network.service after containers/gvisor-tap-vsock#207 is merged.
This makes it more generic so that it can be installed by default.
This PR also gives a more descriptive name to the
vm
binary.