Rpm-ostree rebase from docker registry :latest tag

I’m using a custom manifest.yaml to build a coreos image to install on several servers. Originally I was uploading the .ociarchive file to each server individually by hand, but that scales poorly (my upload bandwidth isn’t great). Now, I’m trying to use a docker registry, but I can’t find an rpm-ostree equivalent to podman pull that actually works.

rpm-ostree rebase ostree-unverified-registry:example.com/my-image:latest

works fine exactly once: the system happily rebases and reboots, and then can never be upgraded. Subsequent attempts at the same command yield

error: Old and new refs are equal: ostree-unverified-registry:example.com/my-image:latest

The alternate form ostree-unverified-image:docker://example.com/my-image:latest does the same thing: rpm-ostree rebase will rebase on it exactly once and then never again. I can’t find anything in rpm-ostree that looks like a “pull” command.

One level lower, ostree does have ostree container image pull, but trying that yields a (predictable) error about the filesystem being read-only:

# ostree container image pull /sysroot/ostree/repo ostree-unverified-image:docker://example.com/my-image:latest
error: Preparing import: Fetching manifest: Writing cached pending manifest: Unable to write detached metadata: open(O_TMPFILE): Read-only file system

I’ve found I can work around this by generating a docker URL in the image@sha syntax using skopeo inspect so that the string passed into rpm-ostree is always unique:

# this works
rpm-ostree rebase ostree-unverified-image:docker://"$( \
  skopeo inspect "docker://example.com/my-image:latest" \
  | jq -r '.Name + "@" + .Digest' )"

but it seems like this is a lot more difficult than it should be. I suspect I’m missing something obvious. Am I supposed to mount -o rw,remount /sysroot to use ostree container image pull? Or is this just a missing feature?

Did you try rpm-ostree upgrade command?
As the rebase is only one time when you need rebase version upgrades
That will update from latest builds and you can enable systemd.timer for automatic updates so it will always update when there is latest on time you give

:person_facepalming: Thank you; I’m stupid. I did try this:

qa1:~# rpm-ostree upgrade --check
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora redacted updates-archive
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264'; generated: 2026-03-24T10:37:04Z solvables: 3
rpm-md repo 'updates'; generated: 2026-11-03T01:30:24Z solvables: 31470
rpm-md repo 'fedora'; generated: 2026-04-22T13:34:32Z solvables: 76354
rpm-md repo 'redacted' (cached); generated: 2026-10-26T16:29:52Z solvables: 54
rpm-md repo 'updates-archive'; generated: 2026-10-31T02:21:19Z solvables: 50850
Note: --check and --preview may be unreliable.  See https://github.com/coreos/rpm-ostree/issues/1579
No updates available.

… I even clicked through to the github issue in the Note: at the end there. For some reason it didn’t occur to me to see what rpm-ostree upgrade on its own would do without the --check flag. It pulls the updated manifest and works fine.