-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't upgrade core machine #22678
Comments
With what version did you create the podman machine VM, the URL was only temporary and not part of 5.0 AFAIK. The proper address is |
@Luap99 I created VM with Podman 5.0.2 with no configs altered. |
@baude PTAL is there something in the machine that hard codes the wrong image path? |
This bug hits users with v5.0 machines who cannot use Rosetta when updating to Podman CLI v5.1 or later. |
@tnk4on Am I understand right that it is fixed in 5.1? |
@m-emelchenkov No, this relates to machine-os.
|
The code for the cause is hard coded below |
This should be fixed to point to the actual image @baude |
Issue Description
podman machine ssh 'sudo rpm-ostree upgrade --check'
failed with errorerror: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: reading manifest 5.0 in quay.io/containers/podman-machine-os: unauthorized: access to the requested resource is not authorized
Steps to reproduce the issue
Steps to reproduce the issue
podman machine init
, macOS 14.4.1 w/ podman 5.0.2 from HomeBrew.podman machine ssh 'sudo rpm-ostree upgrade --check'
.Describe the results you received
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: reading manifest 5.0 in quay.io/containers/podman-machine-os: unauthorized: access to the requested resource is not authorized
Describe the results you expected
It should output list of available updates.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: