[Bug]: Docker compose file not loading when using non-root user in remote server

[maurobender]

Description

Trying to configure an application with Docker compose in Coolify has been really challenging and frustrating.

I've a project with a several docker compose configuration files that work ok in my local computer but when trying to select them from the Coolify instance I'm constantly getting the error Could not load base compose file from /docker-compose.yaml and getting the Docker Compose Location setting back to its original default.

There is no any extra information about why that error is happening, if the file was not found or was any errors parsing it.

I expend a couple of hours trying different file names, and different docker-compose file configuration but without any proper error logs it was imposible to find the error with my docker files.

Then I tried with a new rails project, a clean Dockerfile and docker-compose.yaml file and the error was the same.

I think docker-compose support is kind of broken in this last version.

I'm running the Coolify version v4.0.0-beta.271.

What is strange is that I've another instance with Coolify that is also now in v4.0.0-beta.271 but in that instance since I've install the project a week ago with docker-compose this project is now working. If a try to configure the same project with the same docker-compose.yml file in the brand new instance it does not work :/.

Minimal Reproduction (if possible, example repository)

• Install v4.0.0-beta.271 of Coolify in brand new server.
• Create a project and use this repository as source: https://github.com/maurobender/test-coolify-rails and selecting a remote server.
• Try to select docker compose configuration.

The repository contains:

1. Brand new rails app.
2. Dockerfile
3. docker-compose.yaml file.

Exception or Error

There is not much information about what is happening, the error is Could not load base compose file from /docker-compose.yaml.

Version

v4.0.0-beta.271

[maurobender]

I've done more testing and find that the problem is actually using the Docker compose configuration with a remote server. If I set the resource to run in localhost loading the docker compose file works just fine but if I try to use it in a remote server it doesn't work. Hope this is helpful in order to solve the bug!

[maurobender]

Upon further research I found the problem was using a non-root user (experimental) when connecting to the remote server. Using the root user fixed the issue.

[mcosti]

I'm encountering the same issue

[Sarorn123]

me too

[andrasbacsai]

This will be fixed in the upcoming version.

[truejacobjones]

Hi @andrasbacsai, I have encountered this same bug in beta 297, has this been regressed?

[andrasbacsai]

I will check, but it was hard to reproduce it.

[prplx]

Hi @andrasbacsai, beta 306, docker-compose.yaml file at root of a public repo, the issue is still there

[felipeyousoro]

I'm trying to deploy using the Compose functionality and the issue seems to persist. For more context, the Coolify instance is on another server and I'm using a VPN to access it

• I tried for both public and private repositories, both had the same problem
• Out of curiosity, also tried deploying a Dockerfile to see if it was something related to my repo or permissions, but it worked. So, I guess this is related to Compose

[mclrc]

we are having the same issue, v4.0.0-beta3.13.3 accessing on a remote server. tried renaming the files to the defaults, not using overrides, etc., still does not find it. there is a dockerfile in the same directory as the compose file for the main service, and that is found and built without issues.

[madjsmail]

same !update

i change the extantion to .yml it worked