Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: coolify-testing-host doesn't rebase /data/coolio paths. #1992

Open
chrisbecke opened this issue Apr 14, 2024 · 6 comments
Open

[Bug]: coolify-testing-host doesn't rebase /data/coolio paths. #1992

chrisbecke opened this issue Apr 14, 2024 · 6 comments
Labels
🐞 Confirmed Bug Verified issues that have been reproduced by the team.
Milestone

Comments

@chrisbecke
Copy link

Description

The coolify install.sh script creates /data/coolify folders on the docker host system. However the install of collabsio:coolify-testing-host in docker-compose.windows.yml does not.

The /data/coolify folder is correctly mounted in the coolify-testing-host container, but as it is using /var/run/docker.sock to use the host's docker instance, the host docker can only these files at/home/user/coolify/services/sgso880

Minimal Reproduction (if possible, example repository)

  1. Follow the instructions at Docker Desktop to install the Coolify compose with coolify-testing-host
  2. Create a first user, and project and try to add and deploy the Docker Registry Service as a resource.

Exception or Error

Saved configuration files to /data/coolify/services/sgso880.
Creating Docker network.
Starting service.
Pulling images.
 registry Pulling 
 registry Pulled 
Starting containers.
 Container registry-sgso880  Creating
Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /data/coolify/services/sgso880/auth/registry.password

Version

v4.0.0-beta.258

@andrasbacsai andrasbacsai self-assigned this May 4, 2024
@zgxkbtl
Copy link

zgxkbtl commented Jun 19, 2024

I also use Docker Desktop and have the exact same problem when I create MongoDB resources using a template.

Starting mongodb-database-ro4ws40.
Pulling mongo:7 image.
 kggc8ws Pulling 
 kggc8ws Pulled 
 Volume "mongodb-db-kggc8ws"  Creating
 Volume "mongodb-db-kggc8ws"  Created
 Volume "mongodb-configdb-kggc8ws"  Creating
 Volume "mongodb-configdb-kggc8ws"  Created
 Container kggc8ws  Creating
Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /data/coolify/databases/kggc8ws/docker-entrypoint-initdb.d

Have you figured out a solution for this?

@LEstradioto
Copy link
Contributor

Hey guys, appreciate a look at PR #2710. New option to choose install DIR aka data/coolify... would solve this right?

@Arctomachine
Copy link

It would solve it, but only if it works with windows paths. Currently coolify automatically transforms any path into unix path, it adds / if it is not first symbol.

@LEstradioto
Copy link
Contributor

I see, but we could fix that PR to change docker-compose.windows.yml too I guess

@Arctomachine
Copy link

There is no issue with that particular file, program as whole works fine (mostly). Issues happen in compose files of individual services. For example, install_path/databases/vc40gwc/docker-compose.yml. Manually changing those is pointless, as they are overwritten to default state the moment service starts.

@peaklabs-dev
Copy link
Member

peaklabs-dev commented Sep 22, 2024

If you want to use Coolify for hosting you stuff, please use one of the supported Linux distros as Windows (Windows Server) is not production ready yet. If you are a developer contributing to Coolify, please follow this guide: https://github.com/coollabsio/coolify/blob/main/CONTRIBUTING.md

@peaklabs-dev peaklabs-dev removed their assignment Sep 22, 2024
@peaklabs-dev peaklabs-dev added this to the v4.x.0 milestone Sep 22, 2024
@peaklabs-dev peaklabs-dev added 🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. labels Sep 23, 2024
@peaklabs-dev peaklabs-dev removed the 🐛 Bug Reported issues that need to be reproduced by the team. label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Confirmed Bug Verified issues that have been reproduced by the team.
Projects
None yet
Development

No branches or pull requests

6 participants