Skip to content
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

ci: install latest vagrant #2976

Merged
merged 1 commit into from
Feb 11, 2025
Merged

Conversation

crazy-max
Copy link
Member

relates to #2904 (comment)

@crazy-max crazy-max force-pushed the ci-fix-vagrant branch 2 times, most recently from 00ec90d to 19dbd1d Compare February 10, 2025 14:25
@crazy-max
Copy link
Member Author

crazy-max commented Feb 10, 2025

Installing latest vagrant now gives a 429 on GitHub Actions: https://github.com/docker/buildx/actions/runs/13243084931/job/36962873893#step:6:32 😞

Bringing machine 'default' up with 'libvirt' provider...
Warning: NING] Unrecognized arguments: libvirt_ip_command
==> default: Box 'generic/freebsd14' could not be found. Attempting to find and install...
    default: Box Provider: libvirt
    default: Box Version: >= 0
==> default: Loading metadata for box 'generic/freebsd14'
    default: URL: https://vagrantcloud.com/api/v2/vagrant/generic/freebsd14
==> default: Adding box 'generic/freebsd14' (v4.3.12) for provider: libvirt (amd64)
    default: Downloading: https://vagrantcloud.com/generic/boxes/freebsd14/versions/4.3.12/providers/libvirt/amd64/vagrant.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
The requested URL returned error: 429
Error: Process completed with exit code 1.

So I guess we get rate limited 😢 https://developer.hashicorp.com/vagrant/vagrant-cloud/request-limits#how-do-i-know-if-i-have-been-rate-limited

Checking the headers on CI I get:

< location: https://vagrantcloud.com/generic/boxes/freebsd14/versions/4.3.12/providers/libvirt/amd64/download/vagrant.box
< access-control-allow-credentials: true
< cache-control: no-store, max-age=0
< grpc-metadata-content-type: application/grpc
< grpc-metadata-x-hcp-vagrant-box-registry-ratelimit-limit: 1995/2000
< grpc-metadata-x-hcp-vagrant-box-registry-ratelimit-name: global

But locally I've got x-hcp-vagrant-limit-boxdownloads-remain:

< vary: Accept-Encoding
< x-envoy-upstream-service-time: 3
< x-hcp-vagrant-limit-boxdownloads-remain: 0/20
< x-hcp-vagrant-limit-global-remain: 1957/2000
< x-hcp-vagrant-limit-retry-after: 1739203201

Seems containerd has the same issue: containerd/containerd#11364

Edit: seems fixed now: hashicorp/vagrant#13590 (comment)

@crazy-max crazy-max requested a review from tonistiigi February 10, 2025 19:56
@crazy-max crazy-max changed the title ci: fix vagrant ci: install latest vagrant Feb 10, 2025
@crazy-max crazy-max marked this pull request as ready for review February 10, 2025 20:00
@crazy-max crazy-max requested a review from thaJeztah February 10, 2025 20:00
@crazy-max crazy-max added this to the v0.21.0 milestone Feb 10, 2025
@tonistiigi tonistiigi merged commit 9fe8139 into docker:master Feb 11, 2025
127 checks passed
@crazy-max crazy-max deleted the ci-fix-vagrant branch February 11, 2025 00:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants