This repository has been archived by the owner on May 12, 2021. It is now read-only.
Update dep config file #573
Comments
jodh-intel
added a commit
to jodh-intel/runtimes
that referenced
this issue
Aug 10, 2018
NOP update that simply updates the file format of the `dep` `Gopkg.lock` file to the latest format. Note: `dep ensure` run using `dep` at commit golang/dep@6b79ccc. Fixes kata-containers#573. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
lifupan
pushed a commit
to hyperhq/kata-runtime
that referenced
this issue
Sep 17, 2018
NOP update that simply updates the file format of the `dep` `Gopkg.lock` file to the latest format. Note: `dep ensure` run using `dep` at commit golang/dep@6b79ccc. Fixes kata-containers#573. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
egernst
pushed a commit
to egernst/runtime
that referenced
this issue
Feb 9, 2021
For block devices added by acrn, virtpath is directly udpated in storage.source and so no scanning of PCIAddr is required. This is because, the virtio-blk device is not hot-plugged but added during VM launch and updated later with container rootfs using block rescan feature. v2->v3: 1. Addressed weak match for checking storage block device. 2. Added device check for storage block device. 3. Added negative unit tests for the new code. v1->v2: gofmt'd the mount file. Fixes: kata-containers#573 Signed-off-by: Vijay Dhanraj <vijay.dhanraj@intel.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The format of the
depGopkg.lockfile has changed.As suggested here, let's do a NOP update on its own PR.
The text was updated successfully, but these errors were encountered: