https://github.com/neomutt/test-docker
🐳 Docker experiments
https://github.com/neomutt/test-docker
Last synced: 2 months ago
JSON representation
🐳 Docker experiments
- Host: GitHub
- URL: https://github.com/neomutt/test-docker
- Owner: neomutt
- Created: 2018-11-25T23:16:02.000Z (over 7 years ago)
- Default Branch: main
- Last Pushed: 2022-06-12T19:07:22.000Z (about 4 years ago)
- Last Synced: 2025-12-26T20:57:34.042Z (6 months ago)
- Language: Shell
- Homepage:
- Size: 11.7 KB
- Stars: 2
- Watchers: 6
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Howto
### Build
```sh
git clone https://github.com/neomutt/test-docker
docker build test-docker
# ...
# Lots of logging
# ...
# Successfully built IMAGE_ID
```
To create a named image, use:
```sh
docker build -t dovecot-img test-docker
```
### Run
If you have permission to open ports below 1024 (if you're root),
you can run (constraining those ports only for tcp connections):
```sh
docker run -p 110:110/tcp -p 143:143/tcp -p 993:993/tcp -p 994:994/tcp IMAGE_ID
```
otherwise, run this to map the ports to higher-number ports:
```sh
docker run -P IMAGE_ID
```
You probably don't want to open ports in your system if you don't need to.
Thus, you can tie it too your loopback connection only as follows. By the way,
it seems easier to name the container since you know how to reach it. Also,
you can remove the container as soon as it finish the execution.
```sh
docker run -it --rm --name=dovecot-container \
-p 127.0.0.1:110:110/tcp \
-p 127.0.0.1:143:143/tcp \
-p 127.0.0.1:993:993/tcp \
-p 127.0.0.1:994:994/tcp \
dovecot-img
```
### Access
To get a shell in the Docker, find the ContainerID:
```sh
docker container ls
# CONTAINER ID IMAGE ...
# ae0090e01571 2a24eb92c691 ...
```
then run:
```sh
docker exec -it CONTAINER_ID /bin/sh
```
### Testing
Telnet is the easier way to get a quick check using the dovecot server you
just created
```sh
telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
```
Three users are available in the container:
| User | Password |
| :--------- | :-------- |
| `fulano` | `secret` |
| `cicrano` | `unknown` |
| `beltrano` | `puzzle` |
Again, it is possible to make a quick check while with the telnet open:
```sh
a login fulano secret
```
And list all folders
```sh
a1 list "" *
```
See a full list of raw IMAP commands [here](https://donsutherland.org/crib/imap).
### Cleaning up
The generated images are kept in a hidden place by docker. You can list them doing the following:
```sh
docker images
```
Removing an image is as easy as
```sh
docker rmi
```
However, no container that was created based on that image should exist. To list all the containers in your machine:
```sh
docker ps --all
```
And, to remove a container:
```sh
docker rm
```
### Extra tools
The script `run-container.sh` will create a folder named as `homefs` and than create a container where that folder is used as `\home`. Once the container server is stopped, the container itself will be auto-removed (`--rm`), however all the changes in the homefs will be kept.
**Notes**: To make `homefs` read/writable to the Docker you may also have to:
- Add 'write' file permissions to everything.
`chmod -R og+rwX homefs`
All the files/dirs will appear in the Docker as owned by **your** user id.
- Set the SELinux permissions on the dirs/files
`chcon -Rt svirt_sandbox_file_t homefs`
(For security, Docker isn't allowed to read from a user's home dir).