mirror of
https://github.com/mirage/qubes-mirage-firewall.git
synced 2025-09-19 12:24:44 -04:00
Merge a01c3875d1
into 64d2b16c3a
This commit is contained in:
commit
ed295f7c48
2 changed files with 4 additions and 1 deletions
3
.github/workflows/format.yml
vendored
3
.github/workflows/format.yml
vendored
|
@ -14,6 +14,9 @@ jobs:
|
|||
|
||||
runs-on: ${{ matrix.operating-system }}
|
||||
|
||||
permissions:
|
||||
contents: write
|
||||
|
||||
steps:
|
||||
- name: Checkout code
|
||||
uses: actions/checkout@v4
|
||||
|
|
|
@ -48,7 +48,7 @@ It's OK to install the Docker or Podman package in a template VM if you want it
|
|||
after a reboot, but the build of the firewall itself should be done in a regular AppVM.
|
||||
|
||||
You can also build without that script, as for any normal Mirage unikernel;
|
||||
see [the Mirage installation instructions](https://mirage.io/wiki/install) for details.
|
||||
see [the Mirage installation instructions](https://mirageos.org/wiki/install) for details.
|
||||
|
||||
The build script fixes the versions of the libraries it uses, ensuring that you will get
|
||||
exactly the same binary that is in the release. If you build without it, it will build
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue