This is a docker images with different LTS versions of Ubuntu with a working init process and syslog
Now with 16.04 as latest and 18.04 as beta build
The unix process ID 1 is the process to receive the SIGTERM signal when you execute a
docker stop <container ID>
if the container has the command CMD ["bash"] then bash process will get the SIGTERM signal and terminate.
All other processes running on the system will just stop without the possibility to shutdown correclty
If access to internet the container will automaticly set correct timezone
In this container i have a scipt that handles the init process an uses the supervisor system to start the daemons to run and also catch signals (SIGTERM) to shutdown all processes started by supervisord. This is a modified version of an init script made by Phusion. I've modified it to use supervisor in stead of runit. There are also two directories to run scripts before any daemon is started.
All executable in this directory is run at start, after completion the script is removed from the directory
All executable in this directory is run at every start of the container, ie, at docker run and docker start
Each time the container is started the content of the file /tmp/startup.log is displayed so if your startup scripts generate
vital information to be shown please add that information to that file. This information can be retrieved anytime by
executing docker logs <container id>
In many cases there are som need of things happening att given intervalls, default no cron processs is started in the standard ubuntu image. In this image cron is running together with logrotate to stop the logdfiles to be to big on log running containers.
No all services works without a syslog daemon, if you don't have one running those messages is lost in space, all messages sent via the syslog daemon is saved in /var/log/syslog
Also there are fixed (besides the init process) associated with running ubuntu inside a docker container.
To add other processes to run automatically, add a file ending with .conf in /etc/supervisor/conf.d/ with a layout like this (/etc/supervisor/conf.d/myprogram.conf)
[program:myprogram]
command=/usr/bin/myprogram
myprogram is the name of this process when working with supervisctl.
Output logs std and error is found in /var/log/supervisor/ and the files begins with the <-stdout|-stderr>superervisor*.log
For more settings please consult the manual FOR supervisor
The supervisor process assumes that a command that ends has stopped so if the command detach it will try to restart it. To work around this problem I have written an extra command to be used for these commands. First you have to make a normal start/stop command and place it in the /etc/init.d that starts the program with
/etc/init.d/command start or
service command start
and stops with
/etc/init.d/command stop or
service command stop
Configure the configure-file (/etc/supervisor/conf.d/myprogram.conf)
[program:myprogram]
command=/my_service myprogram
There is an optional parameter, to run a script after a service has start, e.g to run the script /usr/local/bin/postproc.sh av myprogram is started
[program:myprogram]
command=/my_service myprogram /usr/local/bin/postproc.sh
The console output is owned by the my_init process so any output from commands won't show in the docker log. To send a text from any command, either at startup or during run, append the output to the file /var/log/startup.log, e.g sending specific text to log
echo "Application is finished" >> /var/log/startup.log
or output from script
/usr/local/bin/myscript >> /var/log/startlog.log
> docker run -d --name ubuntu nimmis/ubuntu
> docker logs ubuntu
*** open logfile
*** Run files in /etc/my_runonce/
*** Run files in /etc/my_runalways/
*** Running /etc/rc.local...
*** Booting supervisor daemon...
*** Supervisor started as PID 9
2015-08-04 11:34:06,763 CRIT Set uid to user 0
*** Started processes via Supervisor......
crond RUNNING pid 13, uptime 0:00:04
syslog-ng RUNNING pid 12, uptime 0:00:04
> docker exec ubuntu sh -c 'echo "Testmessage to log" >> /var/log/startup.log'
> docker logs ubuntu
*** open logfile
*** Run files in /etc/my_runonce/
*** Run files in /etc/my_runalways/
*** Running /etc/rc.local...
*** Booting supervisor daemon...
*** Supervisor started as PID 9
2015-08-04 11:34:06,763 CRIT Set uid to user 0
*** Started processes via Supervisor......
crond RUNNING pid 13, uptime 0:00:04
syslog-ng RUNNING pid 12, uptime 0:00:04
*** Log: Testmessage to log
>
There are a number of commands that most uses and adds to their build, in this build I've added som commonly used packages
Extra included packages are
- wget
- curl
- zip/unzip
- git
- vim
- nano
- psmisc
- less
- patch
- software-properties-common
This continer should normaly run as a daemon i.e with the -d flag attached
docker run -d nimmis/ubuntu
but if you want to check if all services has been started correctly you can start with the following command
docker run -ti nimmis/ubuntu
the output, if working correctly should be
docker run -ti nimmis/ubuntu14
*** open logfile
*** Run files in /etc/my_runonce/
*** Run files in /etc/my_runalways/
*** Running /etc/rc.local...
*** Booting supervisor daemon...
*** Supervisor started as PID 11
2015-01-02 10:45:43,750 CRIT Set uid to user 0
*** Started processes via Supervisor......
crond RUNNING pid 15, uptime 0:00:02
syslog-ng RUNNING pid 14, uptime 0:00:02
pressing a CTRL-C in that window or running docker stop <container ID> will generate the following output
*** Shutting down supervisor daemon (PID 11)...
*** Killing all processes...
you can the restart that container with
docker start <container ID>
Accessing the container with a bash shell can be done with
docker exec -ti <container ID> /bin/bash
This is the commands and environment variables used inside nimmis based containers for extra functionality
In the default configuration is set to UTC time, if you need it to use the correct time you can change to timezone for the container with this command, syntax is
set_tz <timezone>
To get list of available timezones do
set_tz list
If the docker container har access to internet it will determine the timezone from the obtained IP
Add the environment variable TIMEZONE to the desired timezone, i.e to set timezone to CET Stockhome
docker run -d -e TIMEZONE=Europa/Stockholm nimmis/ubuntu
Execute the command on the container as
docker exec -ti <docker ID> set_tz Europa/Stockholm
Execute the following command, it will list available timezones and then remove the container
docker run --rm nimmis/ubuntu set_tz list
If you have any problems with or questions about this image, please contact us by submitting a ticket through a GitHub issue
- Look to see if someone already filled the bug, if not add a new one.
- Add a good title and description with the following information.
- if possible an copy of the output from cat /etc/BUILDS/* from inside the container
- any logs relevant for the problem
- how the container was started (flags, environment variables, mounted volumes etc)
- any other information that can be helpful
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
This image contains LTS versions of Ubuntu, the versions are nimmis/ubuntu:< tag > where tag is
| Tag | Ubuntu version | size |
|---|---|---|
| latest | latest/16.04 | |
| beta | beta/18.04 |  |
| 16.04 | 16.04 |  |
| 14.04 | 14.04 |  |
| 12.04 | 12.04 |  |
T