Closed builderjer closed 1 year ago
Just ran a manual integration test on latest master
against current pi-gen
and it passed the point you're referring to.
It's very likely you are running into an issue with your image name, see for instance https://stackoverflow.com/questions/48522615/docker-error-invalid-reference-format-repository-name-must-be-lowercase.
First assumption is that image-name
actually must be in lower case. If that's the issue, we could add a respective check in the action's preparation steps.
So I changed these lines in my config file
- uses: usimd/pi-gen-action@master
id: build
with:
# Final image name.
image-name: rasp-ovos-headless-dev
And I still get the same error
I also tried with
- uses: usimid/pi-gen-action@v1
and the same error
Ah, I see. You have an error in docker-opts
, as you're not respecting Docker's CLI convention. docker-opts
being translated as PIGEN_DOCKER_OPTS
is appended to the Docker run call (or, well, actually it's being put somewhere in the middle: https://github.com/RPi-Distro/pi-gen/blob/master/build-docker.sh#L150). Since you're not passing your env as -e NAME=value
, Docker considers this to be the image name.
I see you want to explicitly name the output image file. Still don't get why you're not simply adding a rename step after the pi-gen build. That way you wouldn't have stumbled over this.
I forgot that I changed this here. I do actually rename this with pi-gen directly. Thankyou for your help and patience. Removing the docker-opts
fixes this issue.
Not sure if this goes here or in the actual pi-gen repo, but I will start here.
Describe the bug While building an image, it abruptly stops and says that git is not installed on this system.
To Reproduce Steps to reproduce the behavior: Work flow file
Expected behavior finish the build
Logs