-
Notifications
You must be signed in to change notification settings - Fork 32
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
none-driver: Unexpected HTTP response: 404 on ubuntu-24.04 #565
Comments
4 tasks
9 tasks
7 tasks
I am facing this same issue as well. |
Also facing this. Whats the workaround? |
7 tasks
indiebrain
added a commit
to powerhome/redis-operator
that referenced
this issue
Jan 14, 2025
indiebrain
added a commit
to powerhome/redis-operator
that referenced
this issue
Jan 14, 2025
Related to: - medyagh/setup-minikube#565 - https://github.com/powerhome/redis-operator/actions/runs/12774059053/job/35608701152#step:5:78 ``` Preparing to unpack .../socat_1.8.0.0-4build3_amd64.deb ... Unpacking socat (1.8.0.0-4build3) ... Setting up socat (1.8.0.0-4build3) ... Processing triggers for man-db (2.12.0-4build2) ... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. /usr/bin/lsb_release --short --codename noble Error: Unexpected HTTP response: 404 ```
Please check linked PRs:
Workaround is to fix Ubuntu version for GH runner to 22.04: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to install minikube in a GitHub workflow using the
none
driver on ubuntu-latest (which is now moving to 24.04, see https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/ ) as below:it fails with:
It seems that the error happens when this action tries to download a cri-dockerd 0.3.1 deb package, which doesn't exist for Ubuntu 24.04 "noble".
Actually there isn't a deb package for 24.04 even for the latest cri-dockerd version, see Mirantis/cri-dockerd#361 .
The text was updated successfully, but these errors were encountered: