search

fedora-silverblue / issue-tracker

Fedora Silverblue issue tracker
https://fedoraproject.org/atomic-desktops/silverblue/
126 stars 3 forks source link

New Package Request: wireguard-tools #390

Closed travier closed 1 year ago

travier commented 1 year ago
  1. Is the package installed by default in Fedora Wokrstation? If it is not, we will ask you to open an issue in the issue tracker for the Fedora Workstation Working Group.

It's not installed by default in Workstation as it's easily installed after as needed and not yet fully supported in the GNOME UI (there are work in progress PRs). It's supported in NetworkManager via the command line.

  1. What, if any, are the additional dependencies on the package? What is the output of this command on a system without overides or locally installed packages: 
    $ rpm-ostree install --dry-run <package>

Nothing else.

  1. What is the size of the package and its dependencies? 
    rpm -qi <package>
rpm -qi wireguard-tools-1.0.20210914-3.fc37.x86_64 | grep Size
Size        : 296575
  1. What problem are you trying to solve with this package? Or what functionality does the package provide?

Those are the command line tools to manage Wireguard devices. Most interactions after setup will happen via NetworkManager but some debugging and metric information are currently only available via this tool.

  1. Can the software provided by the package be run from a container? Explain why or why not.

While it can be run from a container, it requires root privileges so it needs to be run a privileged container/toolbox, which is not a usual use case for toolbox where we prefer running rootless.

  1. Can the tool(s) provided by the package be helpful in debugging container runtime issues?

No

  1. Can the tool(s) provided by the package be helpful in debugging networking issues?

Kind of, it's related to networking issues.

  1. Is it possible to layer the package locally via rpm-ostree install <package>? Explain why or why not.

Yes, it is and it works well.

We also had this discussion in Fedora CoreOS and ended up including the tool by default as it's really small, useful for "network" related debugging and needs to be run privileged (thus not in an un-privileged tooblox) so having it included by default is easier.

travier commented 1 year ago

GNOME issue and in-progress PR:

travier commented 1 year ago

Filed in the Workstation Working Group tracker: https://pagure.io/fedora-workstation/issue/353

travier commented 1 year ago

Closing as per the response in https://pagure.io/fedora-workstation/issue/353.

travier commented 1 year ago

For anyone coming to this issue, I've solved it for me by creating a minimal "root" toolbox image with the tools that I need, and that include wireguard-tools: https://github.com/travier/quay-containerfiles/blob/main/toolbox-root/Containerfile