Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • GNOME Boxes GNOME Boxes
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 352
    • Issues 352
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • GNOME BoxesGNOME Boxes
  • Issues
  • #232
Closed
Open
Issue created Jul 17, 2018 by Felipe Borges@felipeborgesMaintainer

Get bridged network working on the Flatpak

The libvirt network bridge is a very desirable feature that we have. It has been problematic across various downstreams because of all sorts of settings: binaries/conf files in various prefixes, user/group permissions, and whatnot.

It would be great to get this working in the flatpak sandbox with zero or minimum requirement of interaction with host APIs.


What I could investigate so far is...

  • These paths shouldn't be hardcoded: src/util-app.vala#L246
  • libvirt needs to find the qemu-bridge-helper binary. @teuf pointed at libvirt/m4/virt-driver-qemu.m4. By replacing /usr/libexec/qemu-bridge-helper with /app/libexec/qemu-bridge-helper I managed to get libvirt to find it.
  • Instead of patching libvirt, it would be nice if this could either be a build option or a config we could set.
Edited Dec 15, 2018 by Felipe Borges
Assignee
Assign to
Time tracking