Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Update virtiofs docs #674

Closed
amshinde opened this issue Jun 18, 2020 · 2 comments · Fixed by #675
Closed

Update virtiofs docs #674

amshinde opened this issue Jun 18, 2020 · 2 comments · Fixed by #675
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team. port-to-2.0 PRs that need to be ported to kata 2.0-dev branch

Comments

@amshinde
Copy link
Member

amshinde commented Jun 18, 2020

Update docs to get rid of nemu. Also add a note to mention the number of pods that can be launched on a system may be limited by the size of /dev/shm.
See : kata-containers/runtime#2766

@amshinde amshinde added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Jun 18, 2020
amshinde added a commit to amshinde/documentation that referenced this issue Jun 18, 2020
Update this document to get rid of any nemu mentions.
Added comment to mention that number of containers that can be
launched may be limited by the size of `/dev/shm`.

Fixes kata-containers#674

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde added a commit to amshinde/documentation that referenced this issue Jun 18, 2020
Update this document to get rid of any nemu mentions.
Added comment to mention that number of containers that can be
launched may be limited by the size of `/dev/shm`.

Fixes kata-containers#674

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde added a commit to amshinde/documentation that referenced this issue Jun 19, 2020
Update this document to get rid of any nemu mentions.
Added comment to mention that number of containers that can be
launched may be limited by the size of `/dev/shm`.

Fixes kata-containers#674

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde added a commit to amshinde/documentation that referenced this issue Jun 19, 2020
Update this document to get rid of any nemu mentions.
Added comment to mention that number of containers that can be
launched may be limited by the size of `/dev/shm`.

Fixes kata-containers#674

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde added a commit to amshinde/documentation that referenced this issue Jun 29, 2020
Update this document to get rid of any nemu mentions.
Added comment to mention that number of containers that can be
launched may be limited by the size of `/dev/shm`.

Fixes kata-containers#674

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
@jodh-intel jodh-intel added the port-to-2.0 PRs that need to be ported to kata 2.0-dev branch label Aug 25, 2020
@jodh-intel
Copy link
Contributor

Need to forward port to 2.0.

@fidencio
Copy link
Member


This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.

Important:

All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.

This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:

If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.


Issue backlog automation moved this from In progress to Done May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team. port-to-2.0 PRs that need to be ported to kata 2.0-dev branch
Projects
Issue backlog
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants