You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
changed the title
[Bug]: Docker compose not working in freshly new instance with Coolify
[Bug]: Docker compose file not loading when using remote server
May 2, 2024
maurobender
changed the title
[Bug]: Docker compose file not loading when using remote server
[Bug]: Docker compose file not loading when using non-root user in remote server
May 2, 2024
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.
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 theDocker 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)
The repository contains:
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
The text was updated successfully, but these errors were encountered: