docker-compose version compatibility for Dokploy
I want to try install Mailcow (https://docs.mailcow.email/getstarted/install/#install-mailcow) but requires docker-compose 2.x and upper to install. Does create problem to dokploy?
10 Replies
We don’t apply any restriction so I don’t know if it will throw an error because the current docker version is around 27.0.x
Actually is about docker-compose version, which says 1.29.2
Okay, upgraded the docker-compose and apparently all seems working. TBA soon if some problems shows up
@iPaderi Are you able to install Mailcow successfully? If yes can you share the details of installion.
Yes I did successfully with some workaround
First of all, I launched the .sh file that generated the .env
I put all of those variables inside dokploy.
Then I launched the service thru his docker composer
(With dokploy) and works fine
@iPaderi Thanks for your reply. I am facing a few issues with volume mounting, ip4, and networking issues. Maybe I am not geeting things right. If you can please provide your docker-compose so that I can compare it with mine. As the docker-compose is so long I am not able to recreate as you did. Thank you in advance
I didn’t touch anything of that. I literally used the same docker composer they provide without tunnelling thru traefik since the machine doesn’t have services that requires port to be tunnelled
Only the 80/443 I’ve manually removed for dokploy and I did the config on Dokploy domains
Port 25/465 etc are only for mail so no needed to pass them on traefik, unless you want multiple instances (that are useless in my opinion)
@iPaderi Thank you for your quick response. I will try your suggestion and post the results. 👍
Hello @iPaderi
I am getting Container mail-server-mailcow-c70a32-dockerapi-mailcow-1 Started
Container mail-server-mailcow-c70a32-olefy-mailcow-1 Started
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/etc/dokploy/compose/mail-server-mailcow-c70a32/code/data/conf/unbound/unbound.conf" to rootfs at "/etc/unbound/unbound.conf": create mount destination for /etc/unbound/unbound.conf mount: cannot mkdir in /var/lib/docker/overlay2/1ee9fa541b57a625f74bf8beaefd874a211b676f5495f55faf184629959653a3/merged/etc/unbound/unbound.conf: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Error ❌
Did you remove them from Environment Settings?
HTTP_PORT=80
HTTP_BIND=
HTTPS_PORT=443
HTTPS_BIND=
And which port you assign in the domain Settings?
I am also facing docker volumes mounting issues
Yes I’ve removed them