Settings redundant and maybe conflicting with bridge network functionality

Machine : remote VPS
Server : Apache2.4
OS distro : Ubuntu 22.04 LTS
DB server and database : MariaDB

Docker image : algoo/tracim


My first ever command line to run a container is shown at the end of this thread

In my configuration of choice to use docker, the Tracim app’s container and the “outside world“ for it to map to, are both on the same host, being it my remote VPS, and both have their respective environment and content location separated :

Image : algoo/tracim
Docker projects root directory at var/lib/docker

*** outside of docker ***
Website e.g., and non-containerized database, set with ISPConfig web server
Website’s root directory at /var/www/clients/client1/web1/web/

I went through following steps so to have Tracim app’s container mapping above mentioned website and database, using docker default bridge network :

  • I create required volumes that the container (tracim app) may map to. The .env file allows to pass the environment variable (database) to the container :


  • I changed MariaDB server’s bind-address to, the IP ADDRESS that is by default assigned to the ISPConfig server’s host (my VPS), so to allow remote connexion from container.

  • I allowed the dbuser to remotly access the database from any host.

//// HELP REQUEST ////
Are above settings enough for the default bridge network to be functional, or does it require some further settings such as the followings ?

  • Add the “APP_URL=value“ variable to the .env file

  • Add a host entry to the container by completing the command line with e.g. : –add-host

docker run --name docorg --env-file .env -p 8080:80 - p 3306:3306 -v ~/var/www/clients/client1/web1/web/tracim/etc:/etc/tracim -v ~/var/www/clients/client1/web1/web/tracim/var:/var/tracim -d algoo/tracim