Fix bug where collect script was looking for Clear Containers images
rather than Kata Containers ones.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Look for other runtime packages (Clear Containers and `runv`-based) in
data collection script.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
The github path to the tests repo is hard wired in lib.sh.
This makes it difficult to test any test repo WIP, as it ends
up calling back to the main repo.
Fix by using any value already set, and only setting to the main
repo if unset.
Fixes: #95
Signed-off-by: Graham whaley <graham.whaley@intel.com>
Add a template that will offer guidance for when users visit the
following URL:
- https://github.com/clearcontainers/runtime/issues/new
Crucially, the template asks the users to run the
`kata-collect-data.sh` script and paste the output direct into the
issue.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Add a data collection script that can be run by users and its output
pasted directly into a github issue.
The script is designed to make diagnosing issues as easy as possible
and its output provides a summary of a Kata Containers system
including:
- Versions of all components.
- Details of container managers.
- Errors found in the system journal.
Fixes#80.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Merge `cli/Makefile` with the top level `Makefile`.
Also includes a Travis config update.
Fixes#88.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Both cc-runtime and runv git submodules can now be removed since
the new folder cli defines the OCI wrapper, and the kata API is
defined and implemented through the virtcontainers package in this
same repository.
Fixes#64
Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
In case of virtio-block, we hotplug devices to a bridge.
We need to remove device from bridge while stopping a
container.
Fixes#82
Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
After hot adding vCPUs in the POD, agent's funtion `onlineCPUMem`
must be called to request the agent to online the vCPUs
fixes#67
Signed-off-by: Julio Montes <julio.montes@intel.com>
Now that the only build project is Kata, remove the remaining code to
support other projects and simplify.
Fixes#76.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Added magic tags for `gometalinter` to ignore two unused `const`s that
form part of an `iota` sequence.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Remove the duplicate static checker script and use the central script
defined in the `tests` repo like all the other components.
Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
We were using code copied from github.com/safchain/ethtool.
Vendor in upstream package instead to use additional
functionality added in.
Fixes#71
Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
Since Go 1.8 users no longer need to have GOPATH set in their environment
for the Go tool chain to work. If GOPATH is set, Go will use it. Otherwise
it defaults to ~/go on linux. As most users store their code in ~/go, they
don't bother setting GOPATH any more. virtcontainers-setup.sh, in its
current form, fails for those users, as it requires GOPATH to be set.
This commit fixes the issue by calling go env "GOPATH" to determine the
correct location of the user's go code. go env "GOPATH" will always
return the correct location, whether GOPATH is set, or not.
Fixes: #63
Signed-off-by: Mark Ryan <mark.d.ryan@intel.com>
We ignore routes that have an ipv6 destination, since hyperstart agent
does not have support for ipv6 currently. We should do the same
for default route that has an ipv6 gateway address.
Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
We ignore routes that have an ipv6 destination, since kata agent
does not have support for ipv6 currently. We should do the same
for default route that has an ipv6 gateway address. We need to
revisit this once we start adding support for ipv6.
Fixes#58
Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
