bootc-fetch-apply-updates.timer/service never run on the composefs backend (`/run/ostree-booted` condition)

Open
#2,578 5 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
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
linux, rust

Research direction

Start by inspecting bootc-fetch-apply-updates.timer and bootc-fetch-apply-updates.service, then trace the boot flow that creates /run/ostree-booted and the existing composefs marker. Verify the update units activate on both backends while retaining the intended bootc-managed-host safeguards, and add regression coverage for each backend.

Written by the indexing model from the issue text.

Description

Describe the bug

On a composefs-backend (sealed / UKI) install, the automatic update units never run:

$ systemctl status bootc-fetch-apply-updates.timer
○ bootc-fetch-apply-updates.timer - Apply bootc updates
     Loaded: loaded (/usr/lib/systemd/system/bootc-fetch-apply-updates.timer; enabled; preset: enabled)
     Active: inactive (dead)
    Trigger: n/a
   Triggers: ● bootc-fetch-apply-updates.service
  Condition: start condition unmet at ...; 8min ago
             └─ ConditionPathExists=/run/ostree-booted was not met

/run/ostree-booted is only created by the ostree backend (ostree-prepare-root). On the composefs backend that service is skipped (ConditionKernelCommandLine=ostree) and no equivalent marker is created, so both bootc-fetch-apply-updates.timer and bootc-fetch-apply-updates.service carry an unmet ConditionPathExists=/run/ostree-booted and stay inactive forever.

Impact

Hosts installed with the composefs backend (e.g. sealed images booting a signed UKI) never fetch or apply updates automatically; they need an explicit bootc upgrade. The units are shipped enabled and there is no composefs-specific equivalent, so this is silent.

Environment
  • bootc 1.16.13 (quay.io/fedora/fedora-bootc:44, systemd 259.9)
  • Installed with bootc install to-disk from a sealed (UKI + composefs + fs-verity) image with systemd-boot + Secure Boot
  • Running as a VM on Proxmox VE 9.2; reproduced on a plain composefs install too
Workaround
# /etc/systemd/system/bootc-fetch-apply-updates.timer.d/10-composefs.conf
[Unit]
ConditionPathExists=

and the same drop-in for bootc-fetch-apply-updates.service. Verified: the timer then becomes active and schedules normally.

Suggested fix

Either drop the condition and let bootc itself decide whether the host is bootc-managed, or use a marker both backends provide (the composefs backend already creates /ostree/bootc; a /run/bootc-booted-style marker or a bootc status check would work).

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.