.gitpod.yml doesn't respect the SHA of a custom Docker image #7179
Labels
meta: stale
This issue/PR is stale and will be closed soon
team: workspace
Issue belongs to the Workspace team
Bug description
I mentioned this issue previously on the community forum but it hasn't been resolved despite the fix in #7052.
Previously, I was able to reference a Docker image by using the commit SHA in the
.gitpod.yml
file.Now it appears the SHA is ignored when the workspace is created. This is apparent because the
latest
tag for the Docker image has Ruby version2.7.2
installed and the image referenced by the SHA has Ruby2.7.3
installed.I've narrowed it down to the SHA in the
.gitpod.yml
file because if I tag the docker image with a different name (jelaniwoods/appdev2021-vanilla-rails-hotfix
in my screenshot) the workspace creates and references the correct image.You can reproduce this by creating a workspace from this repository: https://github.com/jelaniwoods/vanilla-rails
Steps to reproduce
Create a workspace from this repository: https://github.com/appdev-projects/vanilla-rails
See the error message:
Workspace affected
No response
Expected behavior
I expect to be able to specify the SHA of a Docker image in the
.gitpod.yml
file and have that effect the workspace environment.Example repository
This repository uses a SHA in the
.gitpod.yml
and the correct version of the image is not used : https://github.com/appdev-projects/vanilla-railsThis repository uses a tagged version of the same image without a SHA and the there is no issue fetching the correct version of the image: https://github.com/jelaniwoods/vanilla-rails
Anything else?
No response
The text was updated successfully, but these errors were encountered: