-
Notifications
You must be signed in to change notification settings - Fork 244
Closed as not planned
Closed as not planned
Copy link
Labels
area/odo-on-podmanIssues or PRs related to running odo against PodmanIssues or PRs related to running odo against Podmankind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.status/blockedDenotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)
Description
/kind bug
What versions of software are you using?
Operating System: macOS arm64
Output of odo version: 3.9.0
How did you run odo exactly?
odo-darwin-amd64 dev --platform=podman --debug --forward-localhost
Actual behavior
Command fails with error
__
/ \__ Developing using the "new-com1" Devfile
\__/ \ Platform: podman
/ \__/ odo version: v3.9.0
\__/
↪ Running on podman in Dev mode
✗ Deploying pod [4s]
Cleaning up resources
✗ exit status 125:
Complete Podman output:
Error: playing YAML file: choosing an image from manifest list docker://quay.io/devfile/base-developer-image@sha256:27d5ce66a259decb84770ea0d1ce8058a806f39dfcfeed8387f9cf2f29e76480: no image found in image index for architecture arm64, variant "v8", OS linux
Expected behavior
Dev started without errors
Any logs, error output, etc?
M/A
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/odo-on-podmanIssues or PRs related to running odo against PodmanIssues or PRs related to running odo against Podmankind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.status/blockedDenotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)
Type
Projects
Status
Done ✅