You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched other issues and no duplicate issues were found.
I'm convinced that this is not my fault but a bug.
Description
I am using ROS 2 Jazzy and Ubuntu (wsl) 24.04.
Upon writing the command "docker pull ghcr.io/autowarefoundation/autoware:universe-devel-20240921", I get the below message
"no matching manifest for linux/amd64 in the manifest list entries"
Expected behavior
Docker image should pull down
Actual behavior
Getting message "no matching manifest for linux/amd64 in the manifest list entries"
Steps to reproduce
Type command "docker pull ghcr.io/autowarefoundation/autoware:universe-devel-20240921"
Versions
OS: Ubuntu 24.04
ROS 2 Jazzy
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
@theksg Sorry for the confusion, but we have been renaming our docker images recently.
If you want to use autoware from September 21, then try pulling: docker pull ghcr.io/autowarefoundation/autoware:universe-20240921-amd64.
If you want to pull the latest one, run docker pull ghcr.io/autowarefoundation/autoware:universe-devel
Checklist
Description
I am using ROS 2 Jazzy and Ubuntu (wsl) 24.04.
Upon writing the command "docker pull ghcr.io/autowarefoundation/autoware:universe-devel-20240921", I get the below message
"no matching manifest for linux/amd64 in the manifest list entries"
Expected behavior
Docker image should pull down
Actual behavior
Getting message "no matching manifest for linux/amd64 in the manifest list entries"
Steps to reproduce
Versions
OS: Ubuntu 24.04
ROS 2 Jazzy
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: