Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.gitpod.yml doesn't respect the SHA of a custom Docker image #7179

Closed
jelaniwoods opened this issue Dec 10, 2021 · 2 comments
Closed

.gitpod.yml doesn't respect the SHA of a custom Docker image #7179

jelaniwoods opened this issue Dec 10, 2021 · 2 comments
Labels
meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team

Comments

@jelaniwoods
Copy link

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.

image: jelaniwoods/appdev2021-vanilla-rails@sha256:35d5756428cbae11f43a94c92d6c384626b1ead2287738299b6010c4e588e781

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 version 2.7.2 installed and the image referenced by the SHA has Ruby 2.7.3 installed.

Screen Shot 2021-12-10 at 5 18 23 PM

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.

same-mg

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:

Your Ruby version is 2.7.2, but your Gemfile specified 2.7.3

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-rails

This 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

@ajhalili2006
Copy link

There's also a related feature request regarding that, which cache validation can sometimes be a pain: #7149

@jldec jldec added the team: workspace Issue belongs to the Workspace team label Dec 30, 2021
@stale
Copy link

stale bot commented Apr 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Apr 2, 2022
@stale stale bot closed this as completed Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team
Projects
None yet
Development

No branches or pull requests

3 participants