Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/marty90/multidocker
Creates a system where users are forced to login in dedicated independent docker containers.
https://github.com/marty90/multidocker
docker docker-image multiuser virtual-machine
Last synced: about 2 months ago
JSON representation
Creates a system where users are forced to login in dedicated independent docker containers.
- Host: GitHub
- URL: https://github.com/marty90/multidocker
- Owner: marty90
- License: apache-2.0
- Created: 2017-06-24T15:07:05.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-11-27T15:12:56.000Z (about 6 years ago)
- Last Synced: 2024-07-31T21:56:14.915Z (5 months ago)
- Topics: docker, docker-image, multiuser, virtual-machine
- Language: Dockerfile
- Size: 17.6 KB
- Stars: 50
- Watchers: 4
- Forks: 9
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-docker - MultiDocker - Create a secure multi-user Docker machine, where each user is segregated into an indepentent container. (Container Operations / User Interface)
- awesome-linux-containers - MultiDocker
- awesome-docker - MultiDocker - Create a secure multi-user Docker machine, where each user is segregated into an indepentent container. (Container Operations / User Interface)
README
[](https://hub.docker.com/r/martino90/multidocker/builds/)
# MultiDocker
This container creates a system where each new user is forced to login into an independent docker container.
The obtained scenario is similar to a setup where each user is provided a **virtual machine**, but it is implemented with **docker**.
Each user has `root` access within her container and **cannot** access the physical machine nor other users' containers. Thus, this tool is useful to share a machine across different users that need to be root, but need to be isolated eachothers. Compared to per-user virtual machines, `multidocker` has few limitations: (i) users cannot interact with the kernel, (ii) users cannot create other users (only admin can).
Under the hood it leverages the key ideas of [docker-in-docker](https://github.com/jpetazzo/dind) and [dockersh](https://github.com/Yelp/dockersh).
**Warning**:
It has not been designed for being deployed in the wild, nor has been tested by independent auditors.
## 1. Run
Just run.
```
sudo docker run -d --privileged --name multidocker martino90/multidocker
```
The `--privileged` flag is needed as new containers are spawned within this one.
And ssh to the container with:
```
ssh root@
```
`` is the containers's ip address. You can get it with:
```
docker inspect --format '{{ .NetworkSettings.IPAddress }}' multidocker
```
Default password is `toor`. You may want to change it.
Within the container, you are in a standard Ubuntu image with few packets already installed.
**Note 1:** You may want to `run` the container with the `-p [external_port]:22` to make the docker reachable from outside your machine via ssh on the port `[external_port]`.
**Note 2:** If you want to persist the home directory of users on you host machine, you can `run` the container with the `-v :/home` parameter. In this way, all the home dirs of users are saved in ``, and, if you kill and run again `multidocker`, the users will find their files in their home directory.
## 2. Add users
To add a user in the system, ssh as root to the container (see previous point), and type:
```
adduser_docker
```
Alternatively you can run on the host:
```
docker exec -i multidocker adduser_docker
```
This will create a new user. You have to specify the user's password.
You can manipulate the created user with normal bash tool (e.g., `deluser`).
`adduser_docker` is a simple macro that creates a user, and does some magic to force it to login in an independent container.
## 3. Connect as a user
To login as user in the system, ssh to the container:
```
ssh @
```
The user is prompted in **its own** docker container. The base image is `ubuntu`.
This is an independent container, where the user can play and install whatever she wants.
The user has almost the same freedom as in a virtual machine (few limitations are imposed by docker).
You may want to add your ssh public key in `~/.ssh/authorized_keys` to autologin in the shell.
You can logout from the shell, and then login again; the container is **persistent**!
## 4. Resume if the container stops
If the container stops for any reason (the host machine restarted, docker daemon crashed), you can restart `multidocker` with:
```
docker start multidocker
```
If this does not solve, the docker and ssh deamons might be down. Restart them with:
```
docker exec -d multidocker /opt/start_daemons.sh
```