Compose Volume Failure on subpath
ZeroInputCtrl opened this issue · comments
⚠️ Please verify that this bug has NOT been reported before.
- I checked and didn't find similar issue
🛡️ Security Policy
- I agree to have read this project Security Policy
Description
When trying to use the latest volume subpath feature, validation fails and refuses to up the stack. Note this also happens on portainer as well. docker compose up in the stack directory works just fine.
Not sure what is being used for compose validation but it doesn't seem to be up to date with the current documented schema.
root@docker:/stacks/data# docker compose config --quiet && printf "OK\n" || printf "ERROR\n"
=> OK
👟 Reproduction steps
Create a external volume (in my case i'm using cifs)
Create a service in a stack that uses said volume with the volume -> subpath
Save and start the stack
volume example
volumes:
- type: volume
source: appdata
target: /backups
volume:
nocopy: true
subpath: nextcloud
👀 Expected behavior
Stack to be started with no issues
😓 Actual Behavior
error raised
validating /stacks/data/compose.yaml: services.next.volumes.5.volume Additional property subpath is not allowed
Dockge Version
1.4.2
💻 Operating System and Arch
Debian x64
🌐 Browser
Firefox
🐋 Docker Version
26.1.2 - Docker Compose version v2.27.0
🟩 NodeJS Version
No response
📝 Relevant log output
No response
I'm having the same issue. My host machine runs Docker version is 26.1.0 which does support basepath, but louislam/dockge is still on 24.0.7 which I presume is the version that was available at the time of building the ./docker/Base.Dockerfile image for the Dockge 1.4.2 release.
Right, would make sense. Didn't connect that the internal docker versions might not match the docker it's connected to. The last release was 4 months ago which i think puts it just before the feature being cut into a release.
Looking at the dockerfile it looks like this really just needs the dockge base image rebuilt (which re-reading, you said that >.> ). I don't see anything that's pinning the version of docker/compose.
Yeah it took me way too long to figure out the problem lies with dockge, I kept thinking it wasn't implemented yet in docker compose, but once I tried manually bringing up the stack it worked just fine. Hope this can be updated soon!
@Sleavely @mgundelfinger if you want it in the meantime i repackaged the docker image for 1.4.2 to include the latest docker-cli/compose. You can find it here https://hub.docker.com/repository/docker/baneofserenity/dockge/general