tilt-dev / tilt-dev/tilt

Support image digests as valid image refs in outputs_image_ref_to

Open
#5,987 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Description

Expected Behavior

I would expect a valid image digest (like docker.io/foo/bar@sha256:abc123) to be accepted by tilt when using the outputs_image_ref_to field of custom_build.

Current Behavior
Error: Output image ref in file /foo/bar/ref.txt was invalid: Expected reference "docker.io/foo/bar@sha256:afb1ca867b4b0cdf1e948278e874429301daea856f4bf2c698c5cb51d4c336c6" to contain a tag

Image digests are truly immutable and it is surprising behavior that they wouldn't be supported based on https://docs.tilt.dev/custom_build.html#why-tilt-uses-immutable-tags

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at custom_build's outputs_image_ref_to handling and the image-reference validation that currently requires a tag. Compare the documented immutable-tag behavior with digest references such as docker.io/foo/bar@sha256:abc123; done means valid digests are accepted without regressing tagged image references.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devops, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.