Hi, I’ve been given the task of installing the 19.1 version of eGroupware on localhost for testing purposes before we migrate our current installation to docker. My problem is that I cannot access collabora and rocket.chat. All the containers are running, I can access the eGroupware page but when I try to access the rocket chat ip I get “Unknown path” and when I try to access collabora I get a blank page with “ok”. I’m using docker-compose to run all the containers, here is my egroupware yaml `version: '3’
volumes:
sources:
#db:
data:
driver_opts:
type: none
o: bind
# to upgrade an existing non-docker installation most easy is to use the existing
# data directory /var/lib/egroupware AND the host database see below
device: /var/lib/egroupware
# otherwise data is stored in data subdirectory of the current directory
#device: $PWD/data
extra sources with apps not part of egroupware container
extra:
driver_opts:
type: none
o: bind
# location of deprecated EGroupware packages like Wiki, SiteMgr, KnowledgeBase
device: /usr/share/egroupware
#device: $PWD/extra
services:
egroupware:
# setting a default language for a new installation
#environment:
#- LANG=de
image: egroupware/egroupware:latest
# EPL image: download.egroupware.org/egroupware/epl:latest
volumes:
- sources:/usr/share/egroupware
# extra-sources rsync from entry-point into sources
- extra:/usr/share/egroupware-extra
- data:/var/lib/egroupware
# if you want to use the host database:
# 1. comment out the whole db service below AND
# 2. set EGW_DB_HOST=localhost AND
# 3. uncomment the next line and modify the host path, it depends on your distro:
# - RHEL/CentOS /var/lib/mysql/mysql.sock
# - openSUSE/SLE /var/run/mysql/mysql.sock
# - Debian/Ubuntu /var/run/mysqld/mysqld.sock
- /var/run/mysqld/mysqld.sock:/var/run/mysqld/mysqld.sock
# private CA so egroupware can validate your certificate to talk to Collabora or Rocket.Chat
#- /etc/egroupware-docker/private-ca.crt:/usr/local/share/ca-certificates/private-ca.crt:ro
environment:
# MariaDB/MySQL host to use: for internal service use “db”, for host database (socket bind-mounted into container) use “localhost”
- EGW_DB_HOST=localhost
# for internal db service you should to specify a root password here AND in db service
# a database “egroupware” with a random password is created for you on installation (password is stored in header.inc.php in data directory)
#- EGW_DB_ROOT=root
#- EGW_DB_ROOT_PW=secret
# alternativly you can specify an already existing database with full right by the given user!
#- EGW_DB_NAME=egroupware
#- EGW_DB_USER=egroupware
#- EGW_DB_PASS=
restart: always
#DB#depends_on:
#DB#- db
container_name: egroupware
# set the ip-address of your docker host AND your official DNS name so EGroupware
# can access Rocket.Chat or Collabora without the need to go over your firewall
#extra_hosts:
#- "my.host.name:ip-address"
nginx:
image: nginx:stable-alpine
volumes:
- sources:/usr/share/egroupware:ro
# to add a certificate create a certificate.pem containing (in that order)
# 1. private key
# 2. public key
# 3. (optional) chain certificates
# uncomment to the next line
# ./certificate.pem:/etc/ssl/private/certificate.pem
# AND uncomment the three lines starting with “listen 443”, “ssl_certificate”, “ssl_certificate_key” in nginx.conf
- ./egroupware-nginx.conf:/etc/nginx/conf.d/default.conf:ro
ports:
# if no webserver is running on the host, change (first) number to 80 or 443
- “127.0.0.1:8080:80”
#- "4443:443"
depends_on:
- egroupware
container_name: egroupware-nginx
restart: always
run an own MariaDB:10.4 (you can use EGroupware’s database backup and restore to add your existing database)
#DB#db:
#DB# image: mariadb
#DB# environment:
#DB# #- MYSQL_ROOT=root
#DB# - MYSQL_ROOT_PASSWORD=secret
#DB# volumes:
#DB# - db:/var/lib/mysql
#DB# container_name: egroupware-db
automatic updates of all containers daily at 4am
watchtower:
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /root/.docker/config.json:/config.json:ro
environment:
- WATCHTOWER_CLEANUP=true # delete old image after update to not fill up the disk
# for email notifications add your email and mail-server here
#- WATCHTOWER_NOTIFICATIONS=email
#- WATCHTOWER_NOTIFICATIONS_LEVEL=info # possible values: panic, fatal, error, warn, info or debug
#- WATCHTOWER_NOTIFICATION_EMAIL_FROM="watchtower@my-domain.com"
#- WATCHTOWER_NOTIFICATION_EMAIL_TO="me@my-domain.com"
#- WATCHTOWER_NOTIFICATION_EMAIL_SERVER=“mail.my-domain.com” # if you give your MX here, you need no user/password
#- WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=25
#- WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER="watchtower@my-domain.com"
#- WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD="secret"
command: --schedule "0 0 4 * * *"
container_name: egroupware-watchtower
restart: always
`
I was wondering if it’s something from the nginx containers side but after adding the nginx.conf snippets suppiled in the egroupware-collabora and egroupware-rocket the nginx container doesn’t start.
I’d be grateful for some suggestions on what should I change in my config for those services to work
Kind regard, Hubert
