[USER CONFIG PROBLEM] DaviCal Administration Portal

[1975deven]

I am new to Linux world. I've been windows users for past 20 years and now trying to host some tools at my home server. I've successfully installed DaviCal based on docker compose below... My issue is how to access the administration portal so I can add some users and play with it's sharing capabilities. When I access the web portal using local host, web page opens with message reading..."It works!" but not seeing any option to access the administration page. Any help would be greatly appreciated.

version: "3"

services:
db:
image: postgres
volumes:
- pgsql_data:/var/lib/postgresql/data
restart: always
environment:
POSTGRES_PASSWORD: "davical"

app:
image: tuxnvape/davical-standalone
volumes:
- davical_config:/config
restart: always
ports:
- 80:80
environment:
HOST_NAME: "example.org"
PGSQL_ROOT_PASS: "davical"
PASSDAVDB: "davical"
DBHOST: "db"
ADMINDAVICALPASS: "admin"
LANG: "fr_FR.UTF-8"
LC_ALL: "fr_FR.UTF-8"
DAVICAL_LANG: "fr_FR"
UPDATE_FROM_OLD: "false"
volumes:
davical_config:
pgsql_data:

[hleskien]

Are you behind a reverse proxy? Did you change the HOST_NAME variable?

[1975deven]

I am not behind reverse proxy. for hostname variable, i am using local dns name...I also tried ip address and same message...

[1975deven]

I've played around with Baikal and Radicale (both hosted on docker) and both lacks sharing capabilities I am looking for So I wanted to play with DaviCal and see what it has to offer.

[Elrondo46]

Tested with a clean install without problems

[1975deven]

[hleskien]

By which address did you access the DaviCal Container? Your screenshots don't match the posted docker-compose file. Which application do you use to run your containers?

[Elrondo46]

Look that's the localhost, I use podman with a pod, the containers are in the same network.

[Elrondo46]

Where is the logs of containers ?

[Elrondo46]

Your database container is broken 1975deven

For info: Changed to help wanted, and redefine in config problem.

[1975deven]

Answer to your questions bellow...

My exact docker compose file is below...

#version: "3"

services:
db:
image: postgres
volumes:
- ./pgsql_data:/var/lib/postgresql/data
restart: always
environment:
POSTGRES_PASSWORD: "davical"

app:
image: tuxnvape/davical-standalone
volumes:
- ./davical_config:/config
restart: always
ports:
- 8810:80
environment:
HOST_NAME: "davical.example.org"
PGSQL_ROOT_PASS: "davical"
PASSDAVDB: "davical"
DBHOST: "db"
ADMINDAVICALPASS: "admin"
LANG: "en_US.UTF-8"
LC_ALL: "en_US.UTF-8"
DAVICAL_LANG: "en_US"
UPDATE_FROM_OLD: "false"
volumes:
davical_config:
pgsql_data:

---

i left the file as is except for few changes with hostname and language...

Since I am running Pihole for local dns, i pointed hostname above to local 192.168.89.11 ip address in pihole. So i am accessing davical with http://davical.example.org:8810. See attached pic...

I am using debian 13 with docker ce edition and portainer ce to manage my containers. This is installed on my test server to see features of DaviCal.

You stated above that my database container is broken... I pulled the image first using docker compose pull command and then deployed it using docker compose up -d with root user privilege.

Hopefully I've answered all your question....

[1975deven]

database container broken, as you mention above...

docker logs shows following error messages...

   See https://github.com/docker-library/postgres/issues/37 for a (long)
   discussion around this process, and suggestions for how to do so.

in 18+, these Docker images are configured to store database data in a
format which is compatible with "pg_ctlcluster" (specifically, using
major-version-specific directory names). This better reflects how
PostgreSQL itself works, and how upgrades are to be performed.

   See also https://github.com/docker-library/postgres/pull/1259

   Counter to that, there appears to be PostgreSQL data in:
     /var/lib/postgresql/data (unused mount/volume)

   This is usually the result of upgrading the Docker image without
   upgrading the underlying database using "pg_upgrade" (which requires both
   versions).

   The suggested container configuration for 18+ is to place a single mount
   at /var/lib/postgresql which will then place PostgreSQL data in a
   subdirectory, allowing usage of "pg_upgrade --link" without mount point
   boundary issues.

   See https://github.com/docker-library/postgres/issues/37 for a (long)
   discussion around this process, and suggestions for how to do so.

[Elrondo46]

Try UPDATE_FROM_OLD: "false" to true
Remove all before (it's a new install)