This repository has been archived by the owner on May 12, 2021. It is now read-only.
# Kata Containers 0.3.0 #324
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- cli :Implement events command - docs: update README to include links to user guides - versions: Update versions file. - build: default to using qemu-lite-x86_64 - versions: Add gometalinter to versions database - kata-env: Remove static agent version - virtcontainers/qemu: reduce memory footprint 1205e34 cli: implement events command f1f534c vendor: update agent b9c9ad9 docs: update README to include links to user guides 5b4ab7d versions: Update cri-containerd version. 4bfa8f8 versions: Add default initrd information 646e752 versions: Change kernel data. 1382662 build: default to using qemu-lite-x86_64 a0b1083 versions: Add gometalinter to versions database 80bedb0 kata-env: Remove static agent version 4527a80 virtcontainers/qemu: honour CPU constrains 07db945 virtcontainers/qemu: reduce memory footprint Signed-off-by: Jose Carlos Venegas Munoz <[email protected]>
sboeuf
approved these changes
May 18, 2018
Codecov Report
@@ Coverage Diff @@
## master #324 +/- ##
=======================================
Coverage 63.87% 63.87%
=======================================
Files 87 87
Lines 8620 8620
=======================================
Hits 5506 5506
Misses 2530 2530
Partials 584 584Continue to review full report at Codecov.
|
zklei
pushed a commit
to zklei/runtime
that referenced
this pull request
Jun 13, 2019
Run containers that use vsock as communication channel inside VMs (nested environments) randomly fails with following error: ``` Stderr: docker: Error response from daemon: OCI runtime create failed: Failed to check if grpc server is working: context deadline exceeded: unknown. ``` Sometimes the connection with the container's vsock is slow because of kata-runtime disables modern (don't rely on fast MMIO) on some devices including vsocks. This issue can be fixed by increasing the dial timeout. fixes kata-containers#324 Signed-off-by: Julio Montes <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1205e34 cli: implement events command
f1f534c vendor: update agent
b9c9ad9 docs: update README to include links to user guides
5b4ab7d versions: Update cri-containerd version.
4bfa8f8 versions: Add default initrd information
646e752 versions: Change kernel data.
1382662 build: default to using qemu-lite-x86_64
a0b1083 versions: Add gometalinter to versions database
80bedb0 kata-env: Remove static agent version
4527a80 virtcontainers/qemu: honour CPU constrains
07db945 virtcontainers/qemu: reduce memory footprint