Closed jnywong closed 7 months ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
I am starting to think that this error is because there isn't currently a container pushed to the container registry (I am starting from "fresh") when test.yaml
is triggered.
Okay yes, I have confirmed my suspicions above. I needed to make sure that the image defined by DOCKER_REGISTRY
and IMAGE_NAME
is non-empty and initialised with at least one build.
Describe the bug The action fails because the container cannot access the contents of the
image-tests
folder.To Reproduce Steps to reproduce the behavior:
test.yaml
withNO_PUSH: "true"
DOCKER_REGISTRY: "quay.io"
REPO_DIR: /srv/repo
IMAGE_NAME: "jnywong/jupyter-scipy-pytest"
Build the image and push it if
NO_PUSHdisabled
with the error messageExpected behavior The
image-tests
directory exists in my repo, so I expect that this action would be able tols
this folder and run the tests.Additional context The build still fails with the same error message even with an empty
image-tests
folder.Even if you delete the
image-tests
folder entirely the action still fails because the action expects to copy this folder over during the build