Hi, I just installed this container via docker pull on my linux box (OpenSUSE 13.2, docker 1.12.1) and got this log output:

Doing 'start' on site mva:
Preparing tmp directory /omd/sites/mva/tmp...OK
Starting mkeventd...OK
Starting rrdcached...removing stale pid file...OK
Starting npcd...OK
Starting nagios...OK
Starting dedicated Apache for site mva...OK

tail: cannot open '/omd/sites/${CMK_SITE}/var/log/nagios.log' for reading: No such file or directory
tail: no files remaining

... and the container keeps respawning every 5 seconds ...

Greetings

Michael

This docker image unfortunately does not provide volume support so that the container can be deleted and re-created without losing the configured services.
Can you please update the image accordingly?

executing the documented command
docker pull nlmacamp/check_mk:1.4.0p10
I get the messages

Pulling repository docker.io/nlmacamp/check_mk
Tag 1.4.0p10 not found in repository docker.io/nlmacamp/check_mk

Hi, the update.sh is not executable. in the moment you had to add a chmod +x to the update.sh file. is this possible that the file will be modified prior

Thank you for providing a usable Docker version of check_mk (unfortunately the Dockerfile for the check_mk docker version by creator of check_mk is not public (or I couldnt find it).

The only obvious missing thing for me is the graphing. There are graph buttons by default after accessing the Docker based check_mk instance, however PNP4NAGIOS is not installed and thus the images wont load.

Can you implement PNP4NAGIOS support please?

hello

unfortunately I have always the same error when I try to start the container. Any Ideas?

docker-compose file:
check_mk:
image: nlmacamp/check_mk
container_name: check_mk
ports:
- "8080:5000"

volumes:

- /home/docker/check_mk/opt:/opt/backup

restart: always
cap_add:
  - SYS_ADMIN

error:
check_mk | Starting npcd...touch: cannot touch ‘/omd/sites/mva/tmp/pnp4nagios/run/npcd.pid’: No such file or directory
check_mk | chown: cannot access ‘/omd/sites/mva/tmp/pnp4nagios/run/npcd.pid’: No such file or directory
check_mk | An Error occured while reading your config on line 197
check_mk | Message was: "Could not open pidfile '/omd/sites/mva/tmp/pnp4nagios/run/npcd.pid': No such file or directory"
check_mk | OK
check_mk | /omd/sites/mva/etc/rc.d/80-nagios: line 72: /omd/sites/mva/tmp/nagios/nagios.cfg: No such file or directory
check_mk | Nagios configuration file /omd/sites/mva/tmp/nagios/nagios.cfg not found. Terminating...
check_mk | Starting apache...OK
check_mk | Initializing Crontab...OK

cheers,
mrwhite2

Check_MK is now available as official Check_MK Raw Edition Container

https://mathias-kettner.de/check_mk-werks.php?werk_id=6617&HTML=yes
https://hub.docker.com/r/checkmk/check-mk-raw/
http://git.mathias-kettner.de/git/?p=check_mk.git;a=tree;f=docker

Maybe it's a good idea to use this?

I get an error message when running this container, I have tried building it manually and also doing a docker pull.

Docker version being used is: 17.09.0-ce I've also tried 17.12.0-ce

I get this error below:

/opt/bootstrap.sh: line 20: omd: command not found

If the rpm package is installed is that sufficient enough to call on omd or could the ordering be wrong?

I have done a manual pull on my machine and that does not work, I originally had this running as a container using Rancher and it seemed to be working fine but no longer is the case.

First, thanks for this Dockerfile! Super cool to run this software on my server and see resource metrics.

When I run the container, I see repeated messages in my docker daemon logs every minute:

Sep 09 10:12:56 eric-desktop dockerd[986]: time="2018-09-09T10:12:56.446814177-04:00" level=error msg="Error running exec 9a299112e4759a77ca5c8336d217472ebff2f966d8136a0131b in container: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused \"exec: \\\"which\\\": executable file not found in $PATH\": unknown"
Sep 09 10:13:56 eric-desktop dockerd[986]: time="2018-09-09T10:13:56.599305189-04:00" level=error msg="stream copy error: reading from a closed fifo"
Sep 09 10:13:56 eric-desktop dockerd[986]: time="2018-09-09T10:13:56.599604869-04:00" level=error msg="stream copy error: reading from a closed fifo"
Sep 09 10:13:56 eric-desktop dockerd[986]: time="2018-09-09T10:13:56.668032228-04:00" level=error msg="Error running exec 291343cfc65fae8d0da182eb9ee090315373d5fb3c585f71f21 in container: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused \"exec: \\\"which\\\": executable file not found in $PATH\": unknown"
Sep 09 10:14:56 eric-desktop dockerd[986]: time="2018-09-09T10:14:56.402445408-04:00" level=error msg="stream copy error: reading from a closed fifo"
Sep 09 10:14:56 eric-desktop dockerd[986]: time="2018-09-09T10:14:56.403900994-04:00" level=error msg="stream copy error: reading from a closed fifo"
Sep 09 10:14:56 eric-desktop dockerd[986]: time="2018-09-09T10:14:56.456562800-04:00" level=error msg="Error running exec d1cb53f926eeac493e0d95c56e9b3aec4b0e1c566b55a83d50b in container: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused \"exec: \\\"which\\\": executable file not found in $PATH\": unknown"
Sep 09 10:15:56 eric-desktop dockerd[986]: time="2018-09-09T10:15:56.262323225-04:00" level=error msg="stream copy error: reading from a closed fifo"
Sep 09 10:15:56 eric-desktop dockerd[986]: time="2018-09-09T10:15:56.262341025-04:00" level=error msg="stream copy error: reading from a closed fifo"
Sep 09 10:15:56 eric-desktop dockerd[986]: time="2018-09-09T10:15:56.311604038-04:00" level=error msg="Error running exec fec33c2541c176b4c367689452de35772f0e99c42b6aa9ffacc in container: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused \"exec: \\\"which\\\": executable file not found in $PATH\": unknown"
Sep 09 10:16:56 eric-desktop dockerd[986]: time="2018-09-09T10:16:56.586598695-04:00" level=error msg="stream copy error: reading from a closed fifo"
Sep 09 10:16:56 eric-desktop dockerd[986]: time="2018-09-09T10:16:56.586737360-04:00" level=error msg="stream copy error: reading from a closed fifo"

Hi, I am using the image with a mounted folder. The host-folder has 777 permissions but when I start the container it says

tail: cannot open '/var/log/nagios.log' for reading: No such file or directory
tail: no files remaining

My command is
docker run -d --restart always --name check_mk --cap-add=SYS_ADMIN -p 18080:5000 -e CMK_SITE=mysite -e CMK_PASSWORD=abcdefg -v /usr/share/check_mk/data:/opt/omd/sites/mysite nlmacamp/check_mk:1.5.0p3

Without the volume flag the installation works fine!

Working on CentOS 7, docker 1.18

Thanks in advance!

• PR builds / snapshots must not be visible in Docker Hub (like #40)
• Only active tags should be build + available in Docker Hub

Files or locations to have persistant:

• the main configuration file (main.mk)
  

• the final configuration file final.mk, if present
  

• all files in your configuration subdirectory conf.d, if present
  

• automatically inventorized checks (usually /var/lib/check_mk/autochecks)
  

• current performance counters (usually /var/lib/check_mk/counters)
  

• stored logfiles of logwatch (usually /var/lib/check_mk/logwatch)
  

• cached files from the agents (usually /var/lib/check_mk/cache)
  

This image is extremely useful as it is, and I thank you for that, but I cannot figure out how to implement SSL with it. I've tried several methods:

1. Using a bind mount to mount my certs when running the image, installing mod_ssl, configuring /etc/httpd/conf.d/ssl.conf, and updating the /etc/httpd/conf.d/welcome.conf as recommended on the check_mk website

2. Installing mod_ssl, adding certs and httpd config files, and exposing port 443 by way of a new build based off of your image.

3. Building an image from scratch based on the history of your image, adding the necessary certificate and config files, adding mod_ssl to the RUN yum -y install, and exposing port 443.

I just can't seem to get it to work. I feel like I'm missing a crucial step, but I just can't figure out what.

If you actually use this mapping as written then it overwrites the binary omd amongst other things.

If your want to keep your configuration files + performance data persistent, you have to map the /opt/omd directory to the local filesystem like this:

--volume :/opt/omd

K.