ClusterCockpit/cc-docker
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-docker.git synced 2024-12-26 07:19:04 +01:00
Code Issues Packages Projects Releases Wiki Activity
A configurable docker compose setup for development and testing of ClusterCockpit
22 Commits 3 Branches 1 Tag 894 KiB
Shell 53.3%
Perl 33.5%
Dockerfile 12.4%
Makefile 0.8%
8b9f758299
Go to file
Christoph Kluge 8b9f758299 Update README.md
2021-06-10 13:21:59 +02:00
data Prepare docker setup to use fixtures 2021-06-09 09:53:35 +02:00
nginx Prepare docker setup to use fixtures 2021-06-09 09:53:35 +02:00
php-fpm Prepare docker setup to use fixtures 2021-06-09 09:53:35 +02:00
.env Prepare docker setup to use fixtures 2021-06-09 09:53:35 +02:00
docker-compose.yml Prepare docker setup to use fixtures 2021-06-09 09:53:35 +02:00
LICENSE Initial commit 2021-05-19 07:49:23 +02:00
README.md Update README.md 2021-06-10 13:21:59 +02:00

README.md

cc-docker

WARNING: This does not yet work!

This is a setup for docker compose to deploy a complete ClusterCockpit Application Stack including all external components.

At the end it will create containers for:

  • mysql
  • influxdb
  • php-fpm (including the Symfony application)
  • phpmyadmin
  • nginx

Everything is configured in .env.

There exist multiple persistent (shared) volumes:

  • symfony mapping to /var/www/symfony for the ClusterCockpit source tree
  • sql mapping to /var/lib/mysql
  • influxdb/data mapping to /var/lib/influxdb2
  • influxdb/config mapping to /etc//influxdb2
  • logs/nginx mapping to /var/log/nginx
  • logs/symfony mapping to /var/www/symfony/var/log

The containers are build and started using the command:

docker compose up

Desired modes for the future are:

  • Demo Includes everything to try out ClusterCockpit including initial Database Fixtures. No SSL and no reverse Proxy.
  • Develop Only includes all external components of ClusterCockpit. A functional PHP environment and the ClusterCockpit source must be maintained on host machine.
  • Production Includes everything to run ClusterCockpit in a Production environment including SSL and traefic reverse proxy and container orchestration.

TODOS (There are probably a lot more!):

  • Some of the Volume directories need to be created first.
  • ClusterCockpit is at the moment still using the influxDB V1 API, the InfluxDB container is already V2
  • For a complete demo database setup, InfluxDB data fixtures are missing (MySQL demo database is available)

Using for DEMO purpose

Before starting the containers the fixture data needs to be prepared:

  • $ cd data
  • $ ./init.sh

Known Issues:

  • docker-compose installed on Ubuntu (18.04, 20.04) via apt-get can not correctly parse docker-compose.yml due to version differences. Install latest version of docker-compose from https://docs.docker.com/compose/install/ instead.
  • You need to ensure that no other web server is running on port 80 (e.g. Apache2). If port 80 is already in use, edit NGINX_PORT environment variable in .env.
  • Existing VPN connections sometimes cause problems with docker. If docker-compose does not start up correctly, try disabling any active VPN connection. Refer to https://stackoverflow.com/questions/45692255/how-make-openvpn-work-with-docker for further information.

After that from the root of the repository you can start up the containers with:

  • docker-compose up
  • Wait... and wait a little longer

By default, you can access ClusterCockpit in your browser at http://localhost . If NGINX_PORT environment variable was changed, use http://localhost:$PORT .

Credentials for admin user are:

  • User: admin
  • Password: AdminDev

You can shutdown the containers by pressing CTRL-C. Nothing is preserved! After shutting down the container everything is initialized from scratch.

To reuse an existing Symfony tree at ./data/symfony you may remove the environment variable DOCKER_CLUSTERCOCKPIT_INIT in docker-composer.yml file.