notqmail
Docker/Podman builds for notqmail
Dockerfile repository for automated builds.
This docker subdirectory is a repository for Dockerfiles used for building docker/podman images for notqmail. We use Docker Hub for automated builds. However one can create the container images locally by using docker build or podman build command
https://hub.docker.com/r/notqmail/notqmail/tags
The following tags/images can be pulled by executing the commands
a) docker
docker pull notqmail/notqmail:tag
or
b) podman
podman pull notqmail/notqmail:tag
Replace tag in the above command with one of the following
xenial for Ubuntu 16.04
bionic for Ubuntu 18.04
focal for Ubuntu 20.04
centos7 for CentOS 7
centos8 for CentOS 8
debian8 for Debian 8
debian9 for Debian 9
debian10 for Debian 10
fc31 for Fedora Core 31
fc32 for Fedora Core 32
Tumbleweed for openSUSE Tumbleweed
Leap15.2 for openSUSE Leap 15.2
Instructions for starting the docker/podman container
(replace podman with docker for docker operations)
list podman images
$ podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/notqmail centos7 4bcbc7a876fe 38 minutes ago 452 MB
localhost/notqmail focal d3b533841934 2 hours ago 141 MB
Start the podman container
notqmail uses docker-entrypoint to execute qmail-start and start qmail-send, qmail-lspawn, qmail-rspawn. You just need to pass any argument other than notqmail to bypass the default entrypoint.
$ podman run -d -h notqmail.org --name notqmail d3b533841934
08a4df5054d920cfdf8869aa777a7afc39bab19591394ea283c0c082f8b0a876
You can use --net host to map the container's network to the HOST
$ docker run --net host -d -h notqmail.org --name notqmail d3b533841934
or
$ podman run --net host -d -h notqmail.org --name notqmail d3b533841934
Query the id of the container
$ podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
08a4df5054d9 docker.io/cprogrammer/notqmail:focal notqmail About a minute ago Up About a minute ago notqmail
Execute an interactive shell in the container
$ podman exec -ti notqmail /bin/bash
root@notqmail:/#
Get processlist in the container
root@notqmail:/# ps -ef
UID PID PPID C STIME TTY TIME CMD
qmails 1 0 0 10:10 pts/0 00:00:00 qmail-send
qmaill 35 1 0 10:10 pts/0 00:00:00 splogger qmail
root 36 1 0 10:10 pts/0 00:00:00 qmail-lspawn ./Maildir/
qmailr 37 1 0 10:10 pts/0 00:00:00 qmail-rspawn
qmailq 38 1 0 10:10 pts/0 00:00:00 qmail-clean
syslog 50 1 0 10:10 ? 00:00:00 /usr/sbin/rsyslogd
root 66 0 40 10:22 pts/1 00:00:00 bash
root 75 66 0 10:22 pts/1 00:00:00 ps -ef
root@notqmail:/#
Get console logs of the container
$ podman logs
Warning linking /etc/mtab to /proc/self/mounts
Your fully qualified host name is notqmail.org.
Putting notqmail.org into /var/qmail/control/me...
Putting notqmail.org into /var/qmail/control/defaulthost...
Putting notqmail.org into /var/qmail/control/envnoathost...
Putting notqmail.org into /var/qmail/control/defaultdomain...
Putting notqmail.org into /var/qmail/control/plusdomain...
Putting notqmail.org into /var/qmail/control/locals...
Putting notqmail.org into //var/qmail/control/rcpthosts...
Now qmail will refuse to accept SMTP messages except to the following...
notqmail.org
Make sure to change rcpthosts if you add hosts to locals or virtualdomains!
* Starting enhanced syslogd rsyslogd
Stop the container
$ podman stop `podman ps -q`
08a4df5054d920cfdf8869aa777a7afc39bab19591394ea283c0c082f8b0a876
Clear the stopped container image
$ podman rm `podman ps -aq`
08a4df5054d920cfdf8869aa777a7afc39bab19591394ea283c0c082f8b0a876
c) github respository for Dockerfile
The Dockerfile for each of the images is located in a separate subdirectory for each linux distro
notqmail https://github.com/notqmail/docker/tree/master/notqmail
If you want to build the image yourself instead of using hub.docker.com, you can use the below commands. You will need to install either docker or podman using yum/dnf/apt-get
$ docker build -t notqmail:focal ./Dockerfile.focal .
or
$ podman build -t notqmail:focal ./Dockerfile.focal .
NOTE THIS FILE REQUIRES Editing after completing following steps
- ~~create a user docker_user on hub.docker.com (docker_user)~~
- Create a repository for docker files and update point c) above Take a look at
https://github.com/mbhangui/docker & https://hub.docker.com/repository/docker/cprogrammer/indimail-mta
I am interested in knowing what is the motive for bringing Docker into the repository:
- Spinning a container as part of unit tests from time to time.
- Something that packager can use to produce binaries.
- Make a notqmail-from-source runnable docker for users.
- Simply provide the work for whoever want to have a Docker for notqmail.
- All of the above.
- Something else.
I am interested in knowing what is the motive for bringing Docker into the repository:
- Spinning a container as part of unit tests from time to time.
It can be used for testing. Once can put few scripts which sends out emails to some standard email address and a reply is sent back. But I doubt we could be anywhere near achieving that soon. Maybe few months later.
- Something that packager can use to produce binaries. No. The opensuse build service is already doing that. The docker images are being built by exploting the availability of the binary. Theoretically one can also build a docker image by installing make, gcc, git. Pull the source code and install the binary. This could be a better way to test the compilation of notqmail on all the linux distros.
- Make a notqmail-from-source runnable docker for users.
Yes.
- Simply provide the work for whoever want to have a Docker for notqmail.
Docker / podman provides an easy way for a user to quickly run a notqmail instanace on most platforms. Theoretically the user can run a notqmail ubuntu instance on Windows too on a macbook too. Once a docker image is ready, the configuration will be identical for all users.
When you run a docker instance on your production server, you will not be modifiying any files on the server. The docker or podman instance is an isolated container that has everything needed to run notqmail in an isolated container. This gives the ability to the user to minimize changes to his/her existing server (the only change required is to install podman or docker using apt-get, dnf or yum).
The ultimate goal should be to have ucspi-tcp, daemontools also installed. Then one can have a complete mail server setup in a container. Users can simply (regardless of their OS), pull the docker image and run the container using the docker run or the podman run command (using the --net) command. and by doing that the user can have incoming SMTP and outgoing delivery from his server.
Also once you have a deployable podman container for notqmail, one can go to the next step. Deploy kubernetes. I haven't reached there yet. But I know people who have deployed one of my fork of qmail and made a scalable solution.
Adding more directories regarding various build, containerization, integration with other platforms... could mislead those discovering notqmail into thinking that these became part of the build process. Some project even have a Docker file instead of a Makefile.
The convention seems to be that everything that is not part of the project itself starts with a dot, so the same could go for docker.
Or maybe an extra "contrib" directory, or maybe grouping it with the other continuous integration configs #148 could help with standing it clear that notqmail is not tied to GitHub or Docker.
Is there a requirement or a conventions for the location of docker images from projects?
Reading #148 again, it looks like /docker aside to /tests will help keeping the ambiguity away ! :)