Skip to content

[release/2.2] ci: pin fog-json to resolve gem conflict#13714

Merged
samuelkarp merged 1 commit into
containerd:release/2.2from
k8s-infra-cherrypick-robot:cherry-pick-13707-to-release/2.2
Jul 2, 2026
Merged

[release/2.2] ci: pin fog-json to resolve gem conflict#13714
samuelkarp merged 1 commit into
containerd:release/2.2from
k8s-infra-cherrypick-robot:cherry-pick-13707-to-release/2.2

Conversation

@k8s-infra-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #13707

/assign AkihiroSuda

Vagrant 2.4.x bundles an embedded Ruby 3.3.0 runtime that loads the
default specification json-2.7.2 during initialization. When installing
vagrant-libvirt, RubyGems resolves the newly released fog-json 1.4.0,
which requires json (~> 2.19). Because json-2.7.2 is already active in
memory when Vagrant starts up, RubyGems raises a Gem::ConflictError.

To avoid this conflict, pin fog-json to version 1.2.0 before installing
vagrant-libvirt. Since CI caches /root/.vagrant.d across runs, also
uninstall fog-json first to remove any conflicting version left in cache
by a previous job.

Assisted-by: Antigravity
Signed-off-by: Samuel Karp <[email protected]>
@github-project-automation github-project-automation Bot moved this from Needs Triage to Review In Progress in Pull Request Review Jul 2, 2026
@samuelkarp
samuelkarp merged commit 666bec1 into containerd:release/2.2 Jul 2, 2026
51 checks passed
@github-project-automation github-project-automation Bot moved this from Review In Progress to Done in Pull Request Review Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Development

Successfully merging this pull request may close these issues.

3 participants