Can't create a container since the provided tag name is different from the one I provided #660
Comments
|
I've made other tests: docker image ls -a --digests:docker buildx du --verbose:df -h (I wanted to check out if I was running in the same problem that #321):Some metadata from the image built: {
"containerimage.buildinfo": {
"frontend": "dockerfile.v0",
"attrs": {
"filename": "Dockerfile"
},
"sources": [
{
"type": "docker-image",
"ref": "docker.io/library/ubuntu:20.04",
"pin": "sha256:af5efa9c28de78b754777af9b4d850112cad01899a5d37d2617bb94dc63a49aa"
}
]
},
"containerimage.config.digest": "sha256:106b9569abf93c5327b081911e591a6075b2e91abe98e6d46e699d988608d3c4",
"containerimage.descriptor": {
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"digest": "sha256:ad54c506c25078e3ce24580ef7e052400c48a86877373a454ef6017a4f6b582d",
"size": 13286,
"annotations": {
"org.opencontainers.image.created": "2022-08-03T08:23:23Z"
}
},
"containerimage.digest": "sha256:ad54c506c25078e3ce24580ef7e052400c48a86877373a454ef6017a4f6b582d",
"image.name": "docker.io/bitextor/bitextor:testtag"
}Points:
|
|
@cgr71ii I'm not sure, can you give me the link to a pipeline run that fails in https://github.com/bitextor/bitextor/actions with: |
|
Hi! Yes, sure: https://github.com/bitextor/bitextor/runs/7611585308?check_suite_focus=true I didn't provide it because, if I'm not wrong, it's not public. If that's the case, you have attached the logs in the issue. Thank you! |
See nothing that fails with build-push-action or using the resulted image. Wrong link?
|
|
No, it's the right link. I forgot to mention that you should check out the step "Run". It hasn't failed because, if you check the script, it is not expected to fail when |
cgr71ii
added a commit
to bitextor/bitextor
that referenced
this issue
Aug 3, 2022
Docker image is being built manually because the action makes some jobs to fail intermittently: actions/checkout#794 docker/build-push-action#660
|
Hum ok looking at the image being built I think it's the same issue as #321 where load silently fails because of insufficient disk space. You can remove some components pre-installed on the runner in your workflow like dotnet (~23GB): - name: Remove dotnet
run: sudo rm -rf /usr/share/dotnetClosing this issue since that should answer your question and seems a duplicated of #321, but feel free to re-open if it doesn't. Thanks. |
cgr71ii
added a commit
to bitextor/bitextor
that referenced
this issue
Sep 7, 2022
* Fix docker CI script * Fix docker CI script * Fix docker CI script * Fix docker CI script * Fix docker and conda CI scripts * Fix docker and conda CI scripts * Fix docker and conda CI scripts * Fix docker CI script * Update actions/checkout in CI scripts * Update docker CI script docker/build-push-action action * Docker CI script workaround * Add verbose info to docker CI script * Try another version of the docker action * Minor fix * Try actions/checkout@v2 Actions are failing for some reason... * Change conda build boost dependency * Update CI scripts * Minor fix GHA scripts * Update submodules * Update GHA scripts Docker image is being built manually because the action makes some jobs to fail intermittently: actions/checkout#794 docker/build-push-action#660 * Update GHA scripts * Minor fix conda GHA scripts * Update GHA scripts and new docker GHA script * Fix docker GHA script * Fix conda build * Refactor run-tests.sh * Fix conda build * Minor fix * Fix tests * Minor fix intensive tests * Fix typo * Update documentation * Refactor bicleaner train rule Create separate rules for bicleaner model generation based on the flavour * Fix bicleaner AI tests Adding metadata.yaml is not longer necessary * Fix bicleaner rule * Minor fix * Fix dryrun from intensive tests * Fix conda installation in GHA * Fix conda installation in GHA scripts * Fix bicleaner model generation Dictionary train prefix was not being correctly handled Co-authored-by: Leopoldo Pla <leopoldoplasempere@gmail.com> Co-authored-by: Leopoldo Pla <lpla@dlsi.ua.es>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Behaviour
Steps to reproduce this issue
docker run:Expected behaviour
It should create the container and run the tests.
Actual behaviour
But, when
docker runis invoked, it says it doesn't find the image:The value of
${{ env.DOCKER_IMAGE_TAG }}is "bitextor/bitextor:testtag", but looking in the logs, I've found out in the metadata that the image name is "docker.io/bitextor/bitextor:testtag" (is this "docker.io/" prefix expected? At least, in the documentation about testing, they use the same envvar for creating the build and test, and I haven't seen anything about this prefix in the documentation):{ "containerimage.buildinfo": { "frontend": "dockerfile.v0", "attrs": { "filename": "Dockerfile" }, "sources": [ { "type": "docker-image", "ref": "docker.io/library/ubuntu:20.04", "pin": "sha256:fd92c36d3cb9b1d027c4d2a72c6bf0125da82425fc2ca37c414d4f010180dc19" } ] }, "containerimage.config.digest": "sha256:3c0a872aabbd7a90939f2bd9d1bd3cf15a00dcdb0d229ce793655f2459415978", "containerimage.descriptor": { "mediaType": "application/vnd.docker.distribution.manifest.v2+json", "digest": "sha256:7dbf8133fdd907d63ddff7393d2d74a7271fae46741a8082aa2bc5621b00d075", "size": 13286, "annotations": { "org.opencontainers.image.created": "2022-08-01T13:22:32Z" } }, "containerimage.digest": "sha256:7dbf8133fdd907d63ddff7393d2d74a7271fae46741a8082aa2bc5621b00d075", "image.name": "docker.io/bitextor/bitextor:testtag" }Configuration
cibranch)Logs
logs_3461.zip
The text was updated successfully, but these errors were encountered: