[Bug]: docker compose volumes, bind a file is always considered as directory

[Arnaud-IFEA]

Error Message and Logs

from /data/coolify/applications/<project uuid>:

drwxr-x--- 2 debian debian 4096 Jun 24 10:44 grafana.ini

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/data/coolify/applications/ds08wo0gksg08oo4o0cokg4s/grafana.ini" to rootfs at "/etc/grafana/grafana.ini": create mountpoint for /etc/grafana/grafana.ini mount: cannot create subdirectories in "/var/lib/docker/overlay2/0a9f34358f3627017195d34b63abc7b6c5ffd3ce2c693ff48be2a9eee6be9d05/merged/etc/grafana/grafana.ini": not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Steps to Reproduce

1. in the git repo you have an ini file
2. you use a docker compose for resources
3. you set a volume with the ini file with the long syntax and is_directory: false
4. you parse the docker compose in Coolify

Example Repository URL

No response

Coolify Version

v4.0.0-beta.419

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian 12

Additional Information

    volumes:
      - type: bind
        source: ./grafana.ini
        target: /etc/grafana/grafana.ini
        is_directory: false

In the Persistant storage, it is marked as a directory. To date, it seems there is no way to bind a file.

long syntax volumes:

coolify/bootstrap/helpers/shared.php

Lines 1337 to 1339 in afaafd9

	if ((is_null($isDirectory) || ! $isDirectory) && is_null($content)) {
	// if isDirectory is not set (or false) & content is also not set, we assume it is a directory
	$isDirectory = true;

If there is no content i understand that if is_directory is not set you consider it is a directory, but if is_directory: false you should respect the setting and just bind the container to the file no ?

It's the same thing if you use the short syntax:

coolify/bootstrap/helpers/shared.php

Lines 1306 to 1318 in afaafd9

	$foundConfig = $resource->fileStorages()->whereMountPath($target)->first();
	if ($source->startsWith('./') || $source->startsWith('/') || $source->startsWith('~')) {
	$type = str('bind');
	if ($foundConfig) {
	$contentNotNull = data_get($foundConfig, 'content');
	if ($contentNotNull) {
	$content = $contentNotNull;
	}
	$isDirectory = data_get($foundConfig, 'is_directory');
	} else {
	// By default, we cannot determine if the bind is a directory or not, so we set it to directory
	$isDirectory = true;
	}

[djsisson]

@Arnaud-IFEA please note, unless you tick preserve repository, the repo files do not exist on your host, so unless the file exists docker will always assume you are mounting a directory and compose will create one for you if it doesn't exist.

if you want to mount a file, either provide inline content, or create the file beforehand or tick preserve repository. since neither coolify nor docker can bind to a file which doesn't exist, unless you mean you want coolify to create a blank file when loading the compose the first time if is_directory=false and the file doesn't exist? I think coolify just assumes you are going to add the file yourself or tick preserve repo so it will be added before the container is created if you don't provide any content.

[Arnaud-IFEA]

Hello @djsisson , thanks for the answer.
I assumed that coolify was creating a record and copying the file in /data/application/<uui> as it does if you use the persistant storage UI, since the persistant storage is automatically populated by the parsing of the docker compose. But it seems it is not the case, and i have to check the option "preserve repo" to have the server populated with the needed files.

[djsisson]

thats correct, the repo is cloned in its own container, and does not exist on the host unless you specifically tell coolify to keep it

you could also add a build command inside that service, with an inline dockerfile, that just uses 'from the image' and copies in the config file if you don't want to keep the whole repo on your host that way you can remove the volume mounts as the files would be inside the new image

[Arnaud-IFEA]

didn't see you last answer, that's what i've done :).