Closed xynydev closed 7 months ago
Sorry, forgot to update the examples in the readme. The volume needs to be --volume ./iso:/build-container-installer/build
. You can also override the location that the ISO will be written by using ISO_NAME
. Just remember that any path specified is relative to /build-container-installer
unless you specify an absolute path and then it's based on inside the container runtime.
I see, I see. Thanks! That worked splendid. I'll keep this issue up so y'all don't forget to change this in the docs.
I see, I see. Thanks! That worked splendid. I'll keep this issue up so y'all don't forget to change this in the docs.
Glad to hear. And thank you.
Describe the bug When running the container provided by this project to try to build a custom ISO, no files are created into the bind-mounted volume, and no ISO is available after the generation process is complete.
To Reproduce
~/iso/
)docker run --rm --privileged --volume .:/github/workspace/build ghcr.io/jasonn3/build-container-installer:latest VERSION=38 IMAGE_NAME=base IMAGE_TAG=38 VARIANT=Server
sudo
because of how my host is set up.ls
, no ISO file is found.Additional things I tried
docker
:podman
:./iso/
directory with either of these commands.action.yml
to see if the mount path (/github/workspace/
) had changed from when the documentation was written, but I didn't find any indication of such a thing.Expected behavior When running the container with the bind mount, it should output the ISO file into the mounted host directory.
Desktop (please complete the following information):
Additional context
Docker version 24.0.5, build %{shortcommit_cli}
(frommoby-engine
)podman version 4.9.4
(pre-installed)