Open SpuriousGer opened 6 months ago
It will be fixed in the upcoming version.
Excellent, thank you very much!
I'm hitting a similar issue but with nfs
mounts. It seems the issue is not fixed. Tested on v4.0.0-beta.323
The volumes
are ignored and instead new empty volumes are created under Deployable Compose
.
I'm also still having this issue. Running Coolify v4.0.0-beta.360
.
Excerpt of my docker-compose.yaml
:
services:
backend:
build:
context: .
container_name: backend
volumes:
- nfs_images:/app/images
ports:
- 9000:9000
restart: unless-stopped
volumes:
nfs_images:
driver: local
driver_opts:
type: nfs
o: addr=${NFS_SERVER_IP},rw,vers=4.1
device: ":${NFS_DEVICE}"
Logs from the resource deployment:
2024-Oct-28 14:35:57.639960 Oops something is not okay, are you okay? 😢
2024-Oct-28 14:35:57.646766 Volume "z4soo0gc00sgs8o4gkwckoco_nfs_images" Creating
2024-Oct-28 14:35:57.646766 Volume "z4soo0gc00sgs8o4gkwckoco_nfs_images" Created
2024-Oct-28 14:35:57.646766 Container backend-z4soo0gc00sgs8o4gkwckoco-143147453254 Creating
2024-Oct-28 14:35:57.646766 Error response from daemon: failed to populate volume: error while mounting volume '/var/lib/docker/volumes/z4soo0gc00sgs8o4gkwckoco_nfs_images/_data': failed to mount local volume: mount :/mnt/data:/var/lib/docker/volumes/z4soo0gc00sgs8o4gkwckoco_nfs_images/_data, data: addr=xx.xx.xx.xxx: operation not permitted
It seems like Coolify is still making a volume after detecting a nfs
mount and using that in combination with the o
and device
values defined in the docker-compose.yaml
.
I am also having an issue with nfs mounts using docker compose. Wasted hours going in circles trying to find errors and checking permissions but it appears coolify is just stripping the reference to the volume in my service from the deployable compose file for some reason.
Version: v4.0.0-beta.370
Description
I have the following Docker Compose file where I would expect the SMB shares to be mounted but instead they are not mounted and other shares are created:
This is then converted to this deployable Compose and I have no clue why this happens:
I can mount it if I run it locally not through Coolify. This seems to be weird.
Also, why can I not change the storages here:
Minimal Reproduction (if possible, example repository)
Use the Docker Compose file I have above and paste it in a new resource based on Docker Compose.
Exception or Error
No errors occur, but the share it not mounted.
Version
v4.0.0-beta.291