@@ -36,8 +36,7 @@ or `pipx:`
3636pipx install git+https://github.com/xcp-ng/xcp-ng-build-env
3737```
3838
39- After this, two new commands will be available: ` xcp-ng-dev-env-create ` and
40- ` xcp-ng-dev ` .
39+ After this, a new command will be available: ` xcp-ng-dev ` .
4140
4241If you want to develop the package and try the changes as you develop
4342the package, or prefer updating the version from a git repo rather
@@ -63,6 +62,8 @@ Depending on how you installed:
6362* with ` pipx ` : run the same command, with ` --force `
6463* editable with ` git ` : just update your git working tree
6564
65+ Then download the latest image with ` docker pull ghcr.io/xcp-ng/xcp-ng-build-env:8.3 ` or ` podman pull ghcr.io/xcp-ng/xcp-ng-build-env:8.3 ` .
66+
6667## Completion
6768
6869### Bash
@@ -79,15 +80,19 @@ To install the completion, run `register-python-argcomplete --shell fish xcp-ng-
7980
8081## Building the container image(s)
8182
83+ > [ !NOTE]
84+ > The images are typically downloaded from ghcr.io for regular usage.
85+ > Unless you're working on this project, you usually don't need to build the container images yourself.
86+
8287You need one container image per target version of XCP-ng.
8388
84- Clone this repository (outside any container), then use ` xcp-ng-dev-env-create ` to
85- generate the images for the wanted releases of XCP-ng.
89+ Clone this repository (outside any container), then use ` ./container/build.sh ` to
90+ generate the image. Adapt the version to the wanted release of XCP-ng.
8691Note that Docker and Podman store container images separately.
8792
8893```
89- Usage: xcp-ng-dev-env-create {version_of_XCP_ng}
90- ... where {version_of_XCP_ng} is a 'x.y' version such as 8.0.
94+ Usage: ./container/build.sh [--platform PF] <version>
95+ ... where <version> is a 'x.y' version such as 8.0.
9196```
9297
9398## Using the container
0 commit comments