Bound images referenced by tag@digest are pruned right after being pulled

Open
#2,640 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
71/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
backend, devops

Research direction

The issue points to image retention in crates/lib/src/deploy.rs and name handling in crates/lib/src/podstorage.rs. Read the prune comparison around the linked lines, then reproduce with the described .container binding and bootc switch. Done when a bound repo:tag@sha256:digest image remains available after pruning and the reported reboot failure is prevented.

Written by the indexing model from the issue text.

Description

A logically bound image referenced as repo:tag@digest is pulled by bootc switch, then pruned in the same command:

Fetching bound image: docker.io/vaultwarden/server:1.37.5-alpine@sha256:bbe684a0…...done (3 seconds)
Bound images stored: 1
Deploying...done (6 seconds)
Pruned images: 1 (layers: 5, objsize: 73.9 kB)

After the reboot, the app fails with image not known (Pull=never).

Podman stores a repo:tag@digest pull under the name repo@digest, without the tag. The prune keeps an image only if one of its names equals an Image= string exactly:

https://github.com/bootc-dev/bootc/blob/00574d53bd49525cf1f6a58aa0ac259eaef443b3/crates/lib/src/deploy.rs#L461

https://github.com/bootc-dev/bootc/blob/00574d53bd49525cf1f6a58aa0ac259eaef443b3/crates/lib/src/podstorage.rs#L418-L427

so docker.io/vaultwarden/server:1.37.5-alpine@sha256:… never matches docker.io/vaultwarden/server@sha256:….

Reproduce: bind an image with Image=<repo>:<tag>@sha256:<digest> in a .container linked from /usr/lib/bootc/bound-images.d/, then bootc switch to it. Seen with bootc 1.17.1 (Fedora 45); main has the same code. A digest-only reference works.

Dominant language
Rust
Stars
2.3k
Forks
230
Avg merge
2d 11h
Merged PRs (30d)
42

Getting set up

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.

More from bootc-dev/bootc

All issues in bootc-dev/bootc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.