cntr
amicontained
Our great sponsors
| cntr | amicontained | |
|---|---|---|
| 4 | 4 | |
| 637 | 947 | |
| - | 1.5% | |
| 8.5 | 0.0 | |
| 9 days ago | over 3 years ago | |
| Rust | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cntr
-
Discussion: what functionality is Vim missing?
Well for complete remote container it's difficult, but for local ones you can use cntr (https://github.com/Mic92/cntr) which works great.
-
Is there any alternative to the VSCode "Remote - Container" extension for Neovim?
Why exactly would you need that? The beauty of vim is, that you're able to just use it in you container like you would on the host. Create your completely naked container and run cntr attach (https://github.com/Mic92/cntr) and develop like you would do on the host. An alternative approach could be the use of distrobox or Fedora toolbox to achieve the same results.
- cntr - by Mic92 (on github) mounting the file system from one LXC or LXD container or the host into the target container by creating a nested container with the help of a FUSE filesystem.
amicontained
-
Is there a trick to know we're in a container?
If you want a tool based solution to this, tools like amicontained can tell you that in a container and some information about the sandbox.
-
Ask r/kubernetes: What are you working on this week?
I'm looking into SECCOMP profiles as well, but so far is seems a lot of pain for little gain. This series by Paulo Gomes is my starting point. part2 part3 testing-container.
-
Container capabilities
If you want to check the exact syscalls and caps in a container, getting a shell and using something like amicontained https://github.com/genuinetools/amicontained is a good option.
-
Hardening Docker and Kubernetes with seccomp
We made a few changes here. Namely, we changed seccompProfile section where we specify RuntimeDefault type and we also changed the image to amicontained which is a container introspection tool that will tell us which syscalls are blocked, as well as some other interesting security info.
What are some alternatives?
youki - A container runtime written in Rust
runtime - Kata Containers version 1.x runtime (for version 2.x see https://github.com/kata-containers/kata-containers).
vaultwarden - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
Lean and Mean Docker containers - Slim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)
vas-quod - :aerial_tramway: Minimal linux container runtime
kubernetes-ingress - NGINX and NGINX Plus Ingress Controllers for Kubernetes
lxd-snapper - LXD snapshots, automated
labs - This is a collection of tutorials for learning how to use Docker with various tools. Contributions welcome.
docker-compose-wait - A simple script to wait for other docker images to be started while using docker-compose (or Kubernetes or docker stack or whatever)
UBUNTU20-CIS - Ansible role for Ubuntu 2004 CIS Baseline
neovim - Vim-fork focused on extensibility and usability
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more