You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is completly ignored and just some random image name containing a hashes is generated. This block the usage of gitlab-ci, since the resulting image is not pushable to the gitlab registry, since the naming of the docker image does not correspond anymore correctly to the project name. Nevertheless a workaround is at the moment to create a dummy Dockerfile just containing the FROM statement referencing the image name.
But it would be beneficial if the --image-name works for both scenarios ;)
best,
Christian
The text was updated successfully, but these errors were encountered:
invasy
added a commit
to invasy/devcontainers-cli
that referenced
this issue
Jul 5, 2023
- Method `extendImage` created image with the default name ignoring
`--image-name` option.
- The image could not be tagged after building, because CLI exited
with `ERROR: denied: requested access to the resource is denied`
after pushing attempt.
- Added image names from `--image-names` option at building stage.
Hi there,
i was following this guide to setup our internal environment accordingly:
https://containers.dev/guide/gitlab-ci
This works correctly since the devcontainer.json contains the following part:
But as soon as i switch this to just referencing an image name instead of an dockerfile in the devcontainer.json, e.g. via:
The referenced image name via:
is completly ignored and just some random image name containing a hashes is generated. This block the usage of gitlab-ci, since the resulting image is not pushable to the gitlab registry, since the naming of the docker image does not correspond anymore correctly to the project name. Nevertheless a workaround is at the moment to create a dummy Dockerfile just containing the FROM statement referencing the image name.
But it would be beneficial if the
--image-name
works for both scenarios ;)best,
Christian
The text was updated successfully, but these errors were encountered: