builder doc improvements #1520
Open
builder doc improvements #1520
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ydirson
force-pushed
the
qb-doc-improvements
branch
from
0c62559 to
23bbc9a
Compare
Signed-off-by: Yann Dirson <[email protected]>
Signed-off-by: Yann Dirson <[email protected]>
ydirson
force-pushed
the
qb-doc-improvements
branch
from
23bbc9a to
5a29505
Compare
Signed-off-by: Yann Dirson <[email protected]>
rapenne-s
requested changes
Dec 10, 2025
| 3. Installing dependencies | ||
|
|
||
| If you want to use an app qube for developing, install dependencies in the template. If you are using a standalone, install them in the qube itself. Dependencies are specified in ``dependencies-*. txt`` files in the main builder directory (you will also find dependency lists for ``podman`` and ``qubes`` executors if you choose to use thsose), and you can install them easily in the following ways: |
Contributor
There was a problem hiding this comment.
Suggested change
| If you want to use an app qube for developing, install dependencies in the template. If you are using a standalone, install them in the qube itself. Dependencies are specified in ``dependencies-*. txt`` files in the main builder directory (you will also find dependency lists for ``podman`` and ``qubes`` executors if you choose to use thsose), and you can install them easily in the following ways: | |
| If you want to use an app qube for developing, install dependencies in the template. If you are using a standalone, install them in the qube itself. Dependencies are specified in ``dependencies-*. txt`` files in the main builder directory (you will also find dependency lists for ``podman`` and ``qubes`` executors if you choose to use those), and you can install them easily in the following ways: |
| ----- | ||
|
|
||
| This is a simple setup using a docker executor. This is a good default choice; if you don’t know which executor to use, use docker. | ||
| This is a simple setup using a docker or podman executor. This is a good default choice; if you don’t know which executor to use, use docker. Note the podman exector `is known <https://github.com/QubesOS/qubes-issues/issues/10280>` not to be currently able to build DEB packages. |
Contributor
There was a problem hiding this comment.
Suggested change
| This is a simple setup using a docker or podman executor. This is a good default choice; if you don’t know which executor to use, use docker. Note the podman exector `is known <https://github.com/QubesOS/qubes-issues/issues/10280>` not to be currently able to build DEB packages. | |
| This is a simple setup using a docker or podman executor. This is a good default choice; if you don’t know which executor to use, use docker. Note the podman executor `is known <https://github.com/QubesOS/qubes-issues/issues/10280>`__ not to be currently able to build DEB packages. |
Contributor
There was a problem hiding this comment.
you need a __ after the link so it's considered a link
| $ tools/generate-container-image.sh podman | ||
| If you are using ``docker`` and an app qube, as ``/var/lib/docker`` is not persistent by default, you also need to use :doc:`bind-dirs </user/advanced-topics/bind-dirs>` to avoid repeating this step after reboot, adding the following to the ``/rw/config/qubes-bind-dirs.d/docker.conf`` file in this qube: |
Contributor
There was a problem hiding this comment.
Suggested change
| If you are using ``docker`` and an app qube, as ``/var/lib/docker`` is not persistent by default, you also need to use :doc:`bind-dirs </user/advanced-topics/bind-dirs>` to avoid repeating this step after reboot, adding the following to the ``/rw/config/qubes-bind-dirs.d/docker.conf`` file in this qube: | |
| If you are using ``docker`` within an app qube, as ``/var/lib/docker`` is not persistent by default, you also need to use :doc:`bind-dirs </user/advanced-topics/bind-dirs>` to avoid repeating this step after reboot, adding the following to the ``/rw/config/qubes-bind-dirs.d/docker.conf`` file in this qube: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The steps described in this PR allowed me to use
qbwithpodmanin a fc42 qube.This PR relies on files added in QubesOS/qubes-builderv2#218
The big advantages of
podmanoverdockeras I see it, are not requiring to run things as root, and being available in usable form on prominent distros without having to add (and trust) an additional repository.Maybe it would be a good idea to even go further and suggest podman as first choice?actually it seems the podman builder is not ready enough