mirror of
https://github.com/containerd/containerd.git
synced 2026-08-09 17:39:22 +00:00
ci: pin fog-json to resolve gem conflict
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 <samuelkarp@google.com>
This commit is contained in:
committed by
k8s-infra-cherrypick-robot
parent
9c9ad77f45
commit
f89266ecb9
2
.github/workflows/ci.yml
vendored
2
.github/workflows/ci.yml
vendored
@@ -583,6 +583,8 @@ jobs:
|
||||
sudo systemctl enable --now libvirtd
|
||||
sudo apt-get build-dep -y ruby-libvirt
|
||||
sudo apt-get install -y --no-install-recommends libxslt-dev libxml2-dev libvirt-dev ruby-bundler ruby-dev zlib1g-dev
|
||||
sudo env VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 vagrant plugin uninstall fog-json || true
|
||||
sudo env VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 vagrant plugin install fog-json --plugin-version 1.2.0
|
||||
sudo env VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 vagrant plugin install vagrant-libvirt
|
||||
- name: Boot VM
|
||||
run: |
|
||||
|
||||
Reference in New Issue
Block a user