Volume/mount warnings and errors leading to compose failure about docker-suitecrm

[apertureless]

Oh thanks. Will look into this.

[apertureless]

@ClockworkMichael

I am still working on a fix on that.

The probem however is that the config.php will be mounted on the host as a folder. Maybe I missunderstood the docker volume mounting 🤔 I will check the docs and try to fix it.

However, a better fix for you would be to simply create the config.php file. This way the docker-compose would start and you would have the config_overwrites which are working with the ENVS

And more important it would be updateable. SuiteCRM is a bit weird there, because it does not have a config.php per default. It generates one. So if you don't save the config.php in a volume it would be overwritten on every new version.

[ClockworkMichael]

@apertureless when you run this on your machine(s) do you have a local config (perhaps at /srv/docker/suitecrm/upload/config.php that contains anything? Is it an empty file that's added as a volume for persistence?

If it's an empty file for persistence the compose file could be adjusted to be:

 # ... snip ...
  suitecrm:
    build: src
    ports:
      - "8080:80"
    depends_on:
      - mysql
    volumes:
      -  ./upload:/var/www/html/upload
      -  ./config.php:/var/www/html/config.php
    environment:
      DB_TYPE: mysql
      DB_MANAGER: MysqlManager
 # ... snip ...

And then there could be an empty uploads dir and an empty config.php file in the project root (could go elsewhere) that can be filled/used by SuiteCRM as needed.

I've tested this locally with our own docker/php setup and was able to get things working without issue doing something like this.

[apertureless]

Fixed now :)