-
|
(reposting this question from a chat) Am I correct in my understanding that bootc hasn't any concept of image version: when calling bootc update it just compares the IDs of the image and if the remote one is different from the current one, it simply downloads it independent of anything else, creation date or even if the current one is based on the remote one (so functionally "newer")? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Right, we don't consult any metadata in the manifest (whether version or timestamps), only the digest of the manifest. It's the same as Another way to say this is there's no difference between e.g. |
Beta Was this translation helpful? Give feedback.
Right, we don't consult any metadata in the manifest (whether version or timestamps), only the digest of the manifest. It's the same as
podman run --pull=always, and similarly Kubernetes doesn't check any of this by default if you change a pod deployment's image.Another way to say this is there's no difference between e.g.
switchandupgrade- you if you replace quay.io/exampleos/exampleos:latest from rhel9 to rhel10 or the inverse rhel10 to rhel9 -bootc upgradewill fetch and queue the changed image regardless.