19 Replies
I see the same error, the file is created successfully but the content is not passed to the file. The file is empty


@Siumauricio Can you check it out when you have some free time?.
Thankful...
I tested and is working fine this


the file is in the container....
I remember tried something similar to postgres and it was working, so probably you are mapping in a wrong way
Sorry I just did a quick test...
I can see the "Content" data when using the command from your image...
However when accessing the path from "/var/lib/docker/overlay2/edcce412967c36efc9c08d3737385549979f03a7fbef0e88b09b5d1f7421ef50/volume/..." the file is completely empty.
My MariaDB has not changed, the configuration is not optimized added...

This is weird
hmm can you try create a new database but not deploy, create the file mount and then deploy
and check if the content is there...
Yes, I just tested with the procedure you suggested. I created both PostgreSQL and MariaDB. The files are successfully created at /var/lib/docker/overlay2/volume_id/..../merged (or diff)/etc/mysql/conf.d/name_file.cnf
However there is no data, the file is empty
@Siumauricio i am still not getting the acceswer for this - can you help me?
Can you check this? http://docs.dokploy.com/en/docs/core/docker-compose/overview#advanced
Overview
Learn how to use Docker Compose with Dokploy
Can you give more details on why this is needed to use the ../files folder instead of anything else on the host machine ?

Personally I don’t think cleaning volumes automatically if they are not mapped to ../files on the host is a good thing, I think the default docker behavior is the right one with probably an option to click when deploying for cleaning them
not working - as file mount i have tried and did not work with my compose build
so i did cat -> php.ini and added my codes
maybe need to fix that? @Siumauricio
This was previously discussed here https://github.com/Dokploy/docs/issues/15
Please create a minimal reproduce to test that
I haven’t access to this repository :/
Thanks for this ! I understand now ! 🙂