[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
@harrisonqian / Awesome / wiki/platforms/containers.md
Suggest edit
Cancel
Submit suggestion
Title
Name
Note
--- visibility: public --- # Containers **repo:** [Friz-zy/awesome-linux-containers](https://github.com/Friz-zy/awesome-linux-containers) **category:** [[platforms|Platforms]] --- # Awesome Linux Containers [ <img src="https://upload.wikimedia.org/wikipedia/commons/thumb/e/ea/Presidential_Standard_of_Belarus_%28fictional%29.svg/240px-Presidential_Standard_of_Belarus_%28fictional%29.svg.png" width="20" height="20" alt="Voices From Belarus" />](https://bysol.org/en/) [](https://vshymanskyy.github.io/StandWithUkraine) [](https://github.com/sindresorhus/awesome) ## Table of Contents * [About the Author](#About-the-Author) * [Foundations](#foundations) * [Specifications](#specifications) * [Clouds](#clouds) * [Operating Systems](#operating-systems) * [Hypervisors](#hypervisors) * [Containers](#containers) * [Sandboxes](#sandboxes) * [Partial Access](#partial-access) * [Filesystem](#filesystem) * [Dashboard](#dashboard) * [Best practices](#best-practices) * [Security](#security) - [Tools](#tools) - [Links](#links) - [Levels of [security](/@harrisonqian/awesome/wiki/security/security) problems](#levels-of-security-problems) - [Technologies for security](#technologies-for-security) * [Another Information Sources](#another-information-sources) ## About the Author Hello, everyone! My name is Filipp, and I have been working with high load distribution systems and services, security, monitoring, continuous deployment and release management (DevOps domain) since 2012. One of my passions is developing DevOps solutions and contributing to the open-source community. By sharing my knowledge and experiences, I strive to save time for both myself and others while fostering a culture of collaboration and learning. I had to leave my home country, Belarus, due to my participation in [protests against the oppressive regime of dictator Lukashenko](https://en.wikipedia.org/wiki/2020%E2%80%932021_Belarusian_protests), who maintains a close affiliation with Putin. Since then, I'm trying to build my life from zero in other countries. If you are seeking a skilled DevOps lead or architect to enhance your project, I invite you to connect with me on [LinkedIn](https://www.linkedin.com/in/filipp-frizzy-289a0360/) or explore my valuable contributions on [GitHub](https://github.com/Friz-zy/). Let's collaborate and create some cool solutions together :) ## Foundations * [OPEN CONTAINER INITIATIVE](https://www.opencontainers.org/) The Open Container Initiative is a lightweight, open governance structure, to be formed under the auspices of the Linux Foundation, for the express purpose of creating open industry standards around container formats and runtime. * [Cloud Native Computing Foundation](https://cncf.io/) The Cloud Native Computing Foundation will create and drive the adoption of a new set of common container technologies informed by technical merit and end user value, and inspired by Internet-scale computing. * [Cloud Foundry Foundation](https://www.cloudfoundry.org/foundation/) The Cloud is our foundry. ## Specifications * [Open Container Specifications](https://github.com/opencontainers/specs) This project is where the Open Container Initiative Specifications are written. This is a work in progress. * [App Container basics](https://github.com/coreos/rkt/blob/master/Documentation/app-container.md) App Container (appc) is an open specification that defines several aspects of how to run applications in containers: an image format, runtime environment, and discovery protocol. * [Systemd Container Interface](https://wiki.freedesktop.org/www/Software/systemd/ContainerInterface/) Systemd is a suite of basic building blocks for a Linux system. It provides a system and service manager that runs as PID 1 and starts the rest of the system. If you write a container solution, please consider supporting the following interfaces. * [Nulecule Specification](https://github.com/projectatomic/atomicapp/tree/master/docs/spec) Nulecule defines a pattern and model for packaging complex multi-container applications and services, referencing all their dependencies, including orchestration metadata in a container image for building, deploying, monitoring, and active management. * [Oracle microcontainer manifesto](https://blogs.oracle.com/developers/the-microcontainer-manifesto) This is not a new container format, but simply a specific method for constructing a container that allows for better security and stability. * [Cloud Native Application Bundle Specification](https://github.com/deislabs/cnab-spec) A package format specification that describes a technology for bundling, installing, and managing distributed applications, that are by design, cloud agnostic. ## Clouds * [Amazon EC2 Container Service ](https://aws.amazon.com/ecs/) Container management service that supports Docker containers and allows you to easily run applications on a managed cluster of Amazon EC2 instances. * [Google Cloud Platform](https://cloud.google.com/container-engine/) Run Docker containers on Google Cloud Platform, powered by Kubernetes. Google Container Engine actively schedules your containers, based on declared needs, on a managed cluster of virtual machines. * [Jelastic](http://jelastic.com/) Unlimited PaaS and Container-Based IaaS in a Joint Cloud Solution for DevOps. * [Joyent](https://www.joyent.com/) High-Performance Container-Native Infrastructure for Today's Demanding Real-Time Web and Mobile Applications. * [Kubernetes](http://kubernetes.io/) Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops. * [Mesosphere](https://mesosphere.com/) The Mesosphere Datacenter Operating System (DCOS) is a new kind of operating system that spans all of the machines in your datacenter or cloud. It provides a highly elastic, and highly scalable way of deploying applications, services and big data infrastructure on shared resources. * [OpenShift Origin](https://www.openshift.org/) OpenShift Origin is a distribution of [Kubernetes](http://kubernetes.io/) optimized for continuous application development and multi-tenant deployment. Origin adds developer and operations-centric tools on top of Kubernetes to enable rapid application development, easy deployment and scaling, and long-term lifecycle maintenance for small and large teams. * [Warden](https://github.com/cloudfoundry/warden) Manages isolated, ephemeral, and resource controlled environments. Part of Cloud Foundry - the open platform as a service project. * [Virtuozzo](https://virtuozzo.com) A platform, built on Virtuozzo containers, that can be easily run on top of any bare-metal or virtual servers in any public or private cloud, to automate, optimize, and accelerate internal IT and development processes. * [Rancher](http://rancher.com/) Rancher is a complete, open source platform for deploying and managing containers in production. It includes commercially-supported distributions of Kubernetes, Mesos, and Docker Swarm, making it easy to run containerized applications on any infrastructure. * [Docker Swarm](https://docs.[docker](/@harrisonqian/awesome/wiki/back-end-development/docker).com/engine/swarm/) Docker Swarm is native clustering for Docker. * [Azure Container Service](https://azure.microsoft.com/en-us/services/container-service/) Azure Container Service optimizes the configuration of popular open source tools and technologies specifically for Azure. * [CIAO](https://ciao-project.[github](/@harrisonqian/awesome/wiki/development-environment/github).io/) Cloud Integrated Advanced Orchestrator for Intel Clear Linux OS. * [Alibaba Cloud Container Service](https://www.alibabacloud.com/fr/product/container-service) Container Service is a high-performance and scalable container application management service that enables you to use Docker and Kubernetes to manage the lifecycle of containerized applications. * [Nomad](https://www.nomadproject.io/) HashiCorp Nomad is a single binary that schedules applications and services on Linux, Windows, and Mac. It is an open source scheduler that uses a declarative job file for scheduling virtualized, containerized, and standalone applications. ## Operating Systems * [CoreOs](https://coreos.com/) A lightweight Linux operating system designed for clustered deployments providing automation, security, and scalability for your most critical applications. * [RancherOS](http://rancher.com/rancher-os/) RancherOS is a tiny Linux distro that runs the entire OS as Docker containers. * [Project Atomic](http://www.projectatomic.io/) Project Atomic provides the best platform for your Linux Docker Kubernetes (LDK) application stack. Use immutable infrastructure to deploy and scale your containerized applications. * [Snappy Ubuntu Core](https://www.ubuntu.com/cloud/snappy) Ubuntu Core is the perfect system for large-scale cloud container deployments, bringing transactional updates to the world’s favourite container platform. * [ResinOS](https://resinos.io/) A host OS tailored for containers, designed for reliability, proven in production. * [Photon](https://github.com/vmware/photon) Photon OS is a minimal Linux container host designed to have a small footprint and tuned for VMware platforms. Photon is intended to invite collaboration around running containerized and Linux applications in a virtualized environment. * [Clear [Linux](/@harrisonqian/awesome/wiki/platforms/linux) Project](https://clearlinux.org) The Clear Linux Project for Intel Architecture is a distribution built for various Cloud use cases. * [CargOS](https://cargos.io/) CargOS is a new lightweight, open source, platform for Docker hosts that aims for speed, manageability and security. Releases are built for 64-bit Intel/AMD CPUs. * [OSv](http://osv.io/) OSv is the open source operating system designed for the cloud. Built from the ground up for effortless deployment and management, with superior performance. * [HypriotOS](http://blog.hypriot.com/about/) Minimal Debian-based operating systems that is optimized to run Docker. It made it dead easy use Docker on any Raspberry Pi. * [MCL](https://mcl.host) MCL (*Minimal Container Linux*) is a from scratch minimal Linux OS designed specifically to run containers. It has a small footprint of ~50MB and boots within seconds. It is currently optimized to run Docker. ## Hypervisors * [Docker](https://github.com/veggiemonk/awesome-[docker](/@harrisonqian/awesome/wiki/back-end-development/docker)#cloud-infrastructure) An open platform for distributed applications for developers and sysadmins. **Standard de facto**. * [LXD](https://github.com/lxc/lxd) Daemon based on liblxc offering a REST API to manage LXC containers. * [OpenVZ](https://openvz.org/) OpenVZ is container-based virtualization for Linux. OpenVZ creates multiple secure, isolated Linux containers (otherwise known as VEs or VPSs) on a single physical server enabling better server utilization and ensuring that applications do not conflict. * [MultiDocker](https://github.com/marty90/multidocker) Create a secure multi-user Docker machine, where each user is segregated into an indepentent container. * [Lithos](https://github.com/tailhook/lithos/) Lithos is a process supervisor and containerizer for running services. It is not intended to be system init, but rather tries to be a base tool to build container orchestration. * [containerd](https://containerd.io/) A container runtime which can manage a complete container lifecycle - from image transfer/storage to container execution, supervision and networking. ## Containers * [runc](https://github.com/opencontainers/runc) runc is a CLI tool for spawning and running containers according to the OCS specification. * [Bocker](https://github.com/p8952/bocker) Docker implemented in around 100 lines of bash. * [Rocket](https://github.com/coreos/rkt) rkt (pronounced "rock-it") is a CLI for running app containers on Linux. rkt is designed to be composable, secure, and fast. Based on AppC specification. * [LXC](https://github.com/lxc/lxc) LXC is the well known set of tools, templates, library and language bindings. It's pretty low level, very flexible and covers just about every containment feature supported by the upstream kernel. * [Vagga](https://github.com/tailhook/vagga) Vagga is a fully-userspace container engine inspired by Vagrant and Docker, specialized for development environments. * [libct](https://github.com/xemul/libct) Libct is a containers management library which provides convenient API for frontend programs to rule a container during its whole lifetime. * [libvirt](https://libvirt.org/drvlxc.html) A big toolkit to interact with the virtualization capabilities of recent versions of Linux (and other OSes). * [systemd-nspawn](https://wiki.archlinux.org/index.php/Systemd-nspawn) Spawn a namespace container for debugging, testing and building. Part of [systemd](https://wiki.freedesktop.org/www/Software/systemd/). * [porto](https://github.com/yandex/porto) The main goal of Porto is to create a convenient, reliable interface over several Linux kernel mechanism such as cgroups, namespaces, mounts, networking etc. * [udocker](https://github.com/indigo-dc/udocker) A basic user tool to execute simple containers in batch or interactive systems without root privileges. * [Let Me Contain That For You](https://github.com/google/lmctfy) LMCTFY is the open source version of Google’s container stack, which provides Linux application containers. * [cc-oci-runtime](https://github.com/01org/cc-oci-runtime) Intel Clear Linux OCI (Open Containers Initiative) compatible runtime. * [railcar](https://github.com/oracle/railcar) Railcar is a rust implementation of the opencontainers initiative's runtime spec. It is similar to the reference implementation runc, but it is implemented completely in rust for memory safety without needing the overhead of a garbage collector or multiple threads. * [Kata Containers](https://katacontainers.io/) Kata Containers is a new open source project building extremely lightweight virtual machines that seamlessly plug into the containers ecosystem. * [plash](https://github.com/ihucos/plash/) Lightweight, rootless containers. * [runv](https://github.com/hyperhq/runv) Hypervisor-based (KVM, Xen, QEMU) Runtime for OCI. Security by isolation. * [podman](https://github.com/containers/libpod) Full management of container lifecycle. * [firecracker](https://github.com/firecracker-microvm/firecracker) Firecracker runs workloads in lightweight virtual machines, called microVMs, which combine the security and isolation properties provided by hardware virtualization technology with the speed and flexibility of containers. * [sysbox](https://github.com/nestybox/sysbox) Sysbox is a "runc" that creates secure (rootless) containers / pods that run not just microservices, but most workloads that run in VMs (e.g., systemd, Docker, and Kubernetes), seamlessly. * [youki](https://github.com/containers/youki) A container runtime written in Rust. * [footloose](https://github.com/weaveworks/footloose) Containers that look like Virtual Machines. ## Sandboxes * [Firejail](https://l3net.wordpress.com/projects/firejail/) Firejail is a SUID sandbox program that reduces the risk of security breaches by restricting the running environment of untrusted applications using Linux namespaces, seccomp-bpf and Linux capabilities. * [NsJail](https://github.com/google/nsjail) NsJail is a process isolation tool for Linux. It makes use of the namespacing, resource control, and seccomp-bpf syscall filter subsystems of the Linux kernel. * [Subuser](https://github.com/subuser-security/subuser) Securing the Linux desktop with Docker. * [Snappy](https://wiki.ubuntu.com/SecurityTeam/Specifications/SnappyConfinement) Snappy Ubuntu Core is a new rendition of Ubuntu with transactional updates - a minimal server image with the same libraries as today’s Ubuntu, but applications are provided through a simpler mechanism. * [xdg-app](https://wiki.[gnome](/@harrisonqian/awesome/wiki/platforms/gnome).org/Projects/SandboxedApps) xdg-app is a system for building, distributing and running sandboxed desktop applications on Linux. * [Bubblewrap](https://github.com/projectatomic/bubblewrap) Run applications in a sandbox using Linux namespaces without root privileges, with user namespacing provided via setuid binary. * [singularity](https://github.com/singularityware/singularity) Universal application containers for Linux. * [Lxroot](https://github.com/parke/lxroot) Lxroot is a flexible, lightweight, and safer alternative to chroot and/or Docker for non-root users on Linux. ## Partial Access * [nsenter](http://man7.org/linux/man-pages/man1/nsenter.1.html) Run program with namespaces of other processes. Part of the util-linux. * [ip-netns](http://man7.org/linux/man-pages/man8/ip-netns.8.html) Process network namespace management. Part of the iproute2. * [unshare](http://man7.org/linux/man-pages/man1/unshare.1.html) Run program with some namespaces unshared from parent. Part of the util-linux. * [python-nsenter](https://github.com/zalando/python-nsenter) This Python package allows entering Linux kernel namespaces (mount, IPC, net, PID, user and UTS) by doing the "setns" syscall. * [butter](https://pypi.[python](/@harrisonqian/awesome/wiki/programming-languages/python).org/pypi/butter) Python library to interface to low level linux features (inotify, fanotify, timerfd, signalfd, eventfd, containers) with asyncio support. * [pyspaces](https://github.com/Friz-zy/pyspaces) Works with Linux namespaces through glibc with pure python. * [CRIU](https://criu.org/Main_Page) Checkpoint/Restore In Userspace is a software tool for Linux operating system. Using this tool, you can freeze a running application (or part of it) and checkpoint it to a hard drive as a collection of files. CRIU integrated with Docker and LXC to implement Live migration of containers. * [Moby](https://github.com/moby/moby) A "Lego set" of toolkit components for containers software created by Docker. ## Filesystem * [container-diff](https://github.com/GoogleCloudPlatform/container-diff) A tool for analyzing and comparing container images. * [buildah](https://github.com/projectatomic/buildah) A tool which facilitates building OCI container images. * [skopeo](https://github.com/projectatomic/skopeo) Work with remote images registries - retrieving information, images, signing content. * [img](https://github.com/jessfraz/img) Standalone, daemon-less, unprivileged Dockerfile and OCI compatible container image builder. * [dgr](https://github.com/blablacar/dgr) Command line utility designed to build and to configure at runtime App Containers Images (ACI) and App Container Pods (POD) based on convention over configuration. * [Whaler](https://github.com/P3GLEG/Whaler) Whaler is designed to reverse engineer a Docker Image into the Dockerfile that created it. * [dive](https://github.com/wagoodman/dive) A tool for exploring each layer in a docker image. * [go-containerregistry](https://github.com/google/go-containerregistry) Go library and CLIs for working with container registries. * [kaniko](https://github.com/GoogleContainerTools/kaniko) Kaniko is a tool to build container images from a Dockerfile, inside a container or Kubernetes cluster. * [umoci](https://umo.ci/) Umoci is a tool to manipulate OCI container images, and can be used as a rudimentary build tool. * [docker pushrm](https://github.com/christian-korneck/docker-pushrm) A Docker CLI plugin that that lets you push the README.md file from the current directory to a container registry. Supports Docker Hub, Quay and Harbor. ## Dashboard * [LXC-Web-Panel](https://lxc-webpanel.[github](/@harrisonqian/awesome/wiki/development-environment/github).io/) Web panel for LXC on Ubuntu. * [Liman](https://github.com/salihciftci/liman) Basic docker monitoring web application. * [portainer](https://github.com/portainer/portainer) Lightweight Docker management UI. * [swarmpit](https://github.com/swarmpit/swarmpit) Lightweight mobile-friendly Docker Swarm management UI. ## Best practices * [The Twelve-Factor App](https://12factor.net/) The twelve-factor app is a methodology for building software-as-a-service apps. * [Container Best Practices](http://docs.projectatomic.io/container-best-practices/) A collaborative project to document container-based application architecture, creation and management from Project Atomic. ## Security ### Tools * [Docker bench security](https://github.com/docker/docker-bench-security) The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production. * [CoreOS Clair](https://coreos.com/blog/vulnerability-analysis-for-containers/) Open Source Vulnerability Analysis for your Containers. * [bane](https://github.com/jfrazelle/bane) Custom AppArmor profile generator for docker containers. * [OpenSCAP](https://github.com/OpenSCAP/container-compliance) The OpenSCAP ecosystem provides multiple tools to assist administrators and auditors with assessment, measurement and enforcement of security baselines. * [drydock](https://github.com/zuBux/drydock) Drydock provides a flexible way of assessing the security of your Docker daemon configuration and containers using editable audit templates. * [trireme](https://www.aporeto.com/trireme/) Security by segmentation for Docker and Kubernetes. * [goss](https://github.com/aelsabbahy/goss) Quick and Easy server testing/validation. * [sockguard](https://github.com/buildkite/sockguard) A proxy for docker.sock that enforces access control and isolated privileges. * [gvisor](https://github.com/google/gvisor) gVisor is a user-space kernel, written in Go, that implements a substantial portion of the Linux system surface. It includes an Open Container Initiative (OCI) runtime called runsc that provides an isolation boundary between the application and the host kernel. The runsc runtime integrates with Docker and Kubernetes, making it simple to run sandboxed containers. * [docker-explorer](https://github.com/google/docker-explorer/) A tool to help forensicate offline docker acquisitions. * [oci-seccomp-bpf-hook](https://github.com/containers/oci-seccomp-bpf-hook) OCI hook to trace syscalls and generate a seccomp profile. ### Links * [CIS [Security](/@harrisonqian/awesome/wiki/security/security) Benchmarks](https://benchmarks.cisecurity.org/about/) * [Are [Docker](/@harrisonqian/awesome/wiki/back-end-development/docker) containers really secure?](https://opensource.com/business/14/7/docker-[security](/@harrisonqian/awesome/wiki/security/security)-selinux) * [Bringing new [security](/@harrisonqian/awesome/wiki/security/security) features to Docker](https://opensource.com/business/14/9/security-for-docker) * [Docker, [Linux](/@harrisonqian/awesome/wiki/platforms/linux) Containers (LXC), and security](http://www.slideshare.net/jpetazzo/docker-linux-containers-lxc-and-security) * [For containers, [security](/@harrisonqian/awesome/wiki/security/security) is problem #1](http://www.itworld.com/article/2920349/security/for-containers-security-is-problem-1.html) * [Linux Container Security](https://mjg59.dreamwidth.org/33170.html) * [Ask HN: Best [Linux](/@harrisonqian/awesome/wiki/platforms/linux) sandbox?](https://news.ycombinator.com/item?id=10030868) * [CIS [Docker](/@harrisonqian/awesome/wiki/back-end-development/docker) 1.6 Benchmark v1.0.0](https://benchmarks.cisecurity.org/tools2/docker/CIS_Docker_1.6_Benchmark_v1.0.0.pdf) * [Understanding [docker](/@harrisonqian/awesome/wiki/back-end-development/docker) [security](/@harrisonqian/awesome/wiki/security/security) and best practices](https://blog.docker.com/2015/05/understanding-docker-security-and-best-practices/) * [Update on Ubuntu Phone [security](/@harrisonqian/awesome/wiki/security/security) issue](https://insights.ubuntu.com/2015/10/15/update-on-ubuntu-phone-security-issue/) * [Don't expose the [Docker](/@harrisonqian/awesome/wiki/back-end-development/docker) socket (not even to a container)](https://www.lvh.io/posts/dont-expose-the-docker-socket-not-even-to-a-container/) * [RedHat Blog](http://rhelblog.redhat.com/?s=container&submit=Search) - [Introduction to [Linux](/@harrisonqian/awesome/wiki/platforms/linux) Containers](https://access.redhat.com/articles/1353593) - [What’s Next for Containers? User Namespaces](http://rhelblog.redhat.com/2015/07/07/whats-next-for-containers-user-namespaces/#more-1004) - [Architecting Containers Part 1: Why Understanding User Space vs. Kernel Space Matters](http://rhelblog.redhat.com/2015/07/29/architecting-containers-part-1-user-space-vs-kernel-space/) - [Architecting Containers Part 2: Why the User Space Matters](http://rhelblog.redhat.com/2015/09/17/architecting-containers-part-2-why-the-user-space-matters-2/) - [Secure Your Containers with this One Weird Trick](http://rhelblog.redhat.com/2016/10/17/secure-your-containers-with-this-one-weird-trick/) * [Why you shouldn't use ENV variables for secret data](https://diogomonica.com/2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/) * [When to use-[Docker](/@harrisonqian/awesome/wiki/back-end-development/docker) alternatives rkt and LXD](http://searchitoperations.techtarget.com/tip/When-to-use-Docker-alternatives-rkt-and-LXD) * [The container is a lie](https://platform.sh/blog/2020/the-container-is-a-lie/) ### Levels of security problems 1) regular application * always untrusted -> know it * suid bit -> mount with nosuid * limit available syscall -> seccomp-bpf, grsec * leak to another container (bug in namespaces, filesystem) -> user namespaces with different uid inside for each container: 1000 in container - 14293 and 15398 outside; [security](/@harrisonqian/awesome/wiki/security/security) modules like selinux or apparmor 2) system services like cron, ssh * run as root -> isolate via bastion host or vm * using /dev -> "devices" control group The following device nodes are created in the container by default. The Docker images are also mounted with nodev, which means that even if a device node was pre-created in the image, it could not be used by processes within the container to talk to the kernel. /dev/console,/dev/null,/dev/zero,/dev/full,/dev/tty*,/dev/urandom,/dev/random,/dev/fuse * root calls -> capabilities (cap_sys_admin warning!) Here is the current list of capabilities that Docker uses: chown, dac_override, fowner, kill, setgid, setuid, setpcap, net_bind_service, net_raw, sys_chroot, mknod, setfcap, and audit_write. Docker removes several of these capabilities including the following: CAP_SETPCAP Modify process capabilities CAP_SYS_MODULE Insert/Remove kernel modules CAP_SYS_RAWIO Modify Kernel Memory CAP_SYS_PACCT Configure process accounting CAP_SYS_NICE Modify Priority of processes CAP_SYS_RESOURCE Override Resource Limits CAP_SYS_TIME Modify the system clock CAP_SYS_TTY_CONFIG Configure tty devices CAP_AUDIT_WRITE Write the audit log CAP_AUDIT_CONTROL Configure Audit Subsystem CAP_MAC_OVERRIDE Ignore Kernel MAC Policy CAP_MAC_ADMIN Configure MAC Configuration CAP_SYSLOG Modify Kernel printk behavior CAP_NET_ADMIN Configure the network CAP_SYS_ADMIN Catch all uses /proc, /sys -> remount ro, drop cap_sys_admin; security modules like selinux or apparmor; some part of this fs are "namespace-aware" Docker mounts these file systems into the container as "read-only" mount points. . /sys . /proc/sys . /proc/sysrq-trigger . /proc/irq . /proc/bus Copy-on-write file systems Docker uses copy-on-write file systems. This means containers can use the same file system image as the base for the container. When a container writes content to the image, it gets written to a container specific file system. This prevents one container from seeing the changes of another container even if they wrote to the same file system image. Just as important, one container can not change the image content to effect the processes in another container. * uid 0 -> user namespaces, uid 0 mappet to random uid outside 3) system services like devices, network, filesystems * root -> more of services should work on host outside; isolate sensitive functions, run as non-privileged context * full privileges -> isolate on kernel level 4) kernel drivers, network stack, security policies * absolute privileges -> run it in separate vm 5) general like immutable infrastructure * container is ro * write to small separate rw nosuid part [src](http://www.slideshare.net/jpetazzo/docker-linux-containers-lxc-and-security) [src](https://opensource.com/business/14/9/security-for-docker) ### Technologies for security Things are better. For example, most modern container technologies can make use of Linux's built-in security tools such as: [AppArmor](http://wiki.apparmor.net/index.php/Main_Page), [SELinux](http://selinuxproject.org/page/Main_Page) and [Seccomp](http://man7.org/linux/man-pages/man2/seccomp.2.html) policies; [Grsecurity](https://grsecurity.net/); [Control groups (cgroups)](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/ch01.html); [Kernel namespaces](http://man7.org/linux/man-pages/man7/namespaces.7.html) [src](http://www.itworld.com/article/2920349/security/for-containers-security-is-problem-1.html) Sure, you're deploying seccomp, but you can't use selinux inside your container, because the policy isn't per-namespace (?? lxc uses apparmore for each container...) [sVirt](http://selinuxproject.org/page/SVirt) - selinux for kvm [src](https://mjg59.dreamwidth.org/33170.html) Major kernel subsystems are not namespaced like: - SELinux - Cgroups - file systems under /sys - /proc/sys, /proc/sysrq-trigger, /proc/irq, /proc/bus Devices are not namespaced: - /dev/mem - /dev/sd* file system devices - kernel modules If you can communicate or attack one of these as a privileged process, you can own the system. [src](https://opensource.com/business/14/7/docker-security-selinux) ## Another Information Sources * [sysdig-container-ecosystem](https://github.com/draios/sysdig-container-ecosystem) The ecosystem of awesome new technologies emerging around containers and microservices can be a little overwhelming, to say the least. We thought we might be able to help: welcome to the Container Ecosystem Project. * [doger.io](http://doger.io/) This page is an attempt to document the ins and outs of containers on Linux. This is not just restricted to programmers looking to implement containers or use container like features in their own code but also Sysadmins and Users who want to get more of a handle on how containers work 'under the hood'.