omv-extras 6.3 / openmediavault-compose 6.7

ryecoaaron

Not sure what is going on here, but I just installed Nextcloud as well in the VM.. Same thing.. put a compose file in the plugin, and used the "UP" button to pull it. NC started just fine, but isn't showing in my container listing.

Quote from ryecoaaron

Well, the compose plugin container list hasn't changed in a long time. Does your shared folder have space(s) in it? What is the full path to the compose files folder?

No. It's just called "compose"

/srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose

My Volumes being symlinks wouldn't cause this would it?

In the plugin, my "containers" folder, is the full UUID, not a symlink. All of my compose files however, use symlinks

Quote from ryecoaaron

How? The plugin doesn't symlink anything.

I mean my docker-compose volumes are all symlinks...

docker repo enabled.

root@omv6-test:~# ls -al  /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.yml

docker-compose --file /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.yml --env /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.env ps --all --format "json"
-rw-r--r-- 1 root users 573 May 29 18:42 /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.yml
List containers.

Usage: ps [options] [SERVICE...]

Options:
    -q, --quiet          Only display IDs
    --services           Display services
    --filter KEY=VAL     Filter services by a property
    -a, --all            Show all stopped containers (including those created by the run command)
root@omv6-test:~# 

Quote from ryecoaaron

Sorry, i had a typo in my docker-compose command. How about:

docker-compose --file /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.yml --env-file /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.env ps --all --format "json"

Code

$ docker-compose --file /srv/dev-disk-by-uuid-f4986fb7-838b-41ab-bc30-cfd22e29a4d1/composeFiles/portainer/portainer.yml --env-file /srv/dev-disk-by-uuid-f4986fb7-838b-41ab-bc30-cfd22e29a4d1/composeFiles/portainer/portainer.env ps --all --format "json"
[{"ID":"ecbc4d19da6d7b2e43c550ec66a75e054d9182797e3303de962f5a17fe8aedc7","Name":"portainer","Image":"portainer/portainer-ce:latest","Command":"/portainer","Project":"portainer","Service":"portainer","Created":1685401659,"State":"running","Status":"Up 39 minutes","Health":"","ExitCode":0,"Publishers":[{"URL":"","TargetPort":8000,"PublishedPort":0,"Protocol":"tcp"},{"URL":"0.0.0.0","TargetPort":9000,"PublishedPort":9000,"Protocol":"tcp"},{"URL":"::","TargetPort":9000,"PublishedPort":9000,"Protocol":"tcp"},{"URL":"","TargetPort":9443,"PublishedPort":0,"Protocol":"tcp"}]}]

root@omv6-test:~# docker-compose --file /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.yml --env-file /srv/dev-disk-by-uuid-de4d3cf0-f186-4a01-9c75-d518c66176c5/compose/portainer/portainer.env ps --all --format "json"
List containers.

Usage: ps [options] [SERVICE...]

Options:
    -q, --quiet          Only display IDs
    --services           Display services
    --filter KEY=VAL     Filter services by a property
    -a, --all            Show all stopped containers (including those created by the run command)
root@omv6-test:~# 

Yeah there's something weird here. Obviously mine aren't showing with that command, but if I run docker ps in an ssh session, I see them running (and they are working fine)... but I've uploaded their compose files in the compose plugin.

Quote from ryecoaaron

What is the output of: dpkg -l | grep docker

root@omv6-test:~# dpkg -l | grep docker
ii  docker-ce                         5:24.0.2-1~debian.11~bullseye  amd64        Docker: the open-source application container engine
ii  docker-ce-cli                     5:24.0.2-1~debian.11~bullseye  amd64        Docker CLI: the open-source application container engine
ii  docker-compose                    1.25.0-1                       all          Punctual, lightweight development environments using Docker
ii  docker-compose-plugin             2.18.1-1~debian.11~bullseye    amd64        Docker Compose (V2) plugin for the Docker CLI.
ii  python3-docker                    4.1.0-1.2                      all          Python 3 wrapper to access docker.io's control socket
ii  python3-dockerpty                 0.4.1-2                        all          Pseudo-tty handler for docker Python client (Python 3.x)
root@omv6-test:~# 

Quote from ryecoaaron

And

whereis docker-compose

root@omv6-test:~# whereis docker-compose

docker-compose: /usr/bin/docker-compose /usr/share/man/man1/docker-compose.1.gz

root@omv6-test:~#

That may be part of the problem, as I said before, I had to install docker-compose manually to get the plugin to even work.

Quote from ryecoaaron

I'm pretty sure you are using the old version of docker-compose. I would start with removing docker-compose

sudo apt-get install docker-compose

That's weird as I installed it right after I installed the plugin.

Thanks for the effort... hopefully it sorts this out for other users to.

So I just updated and saw the compose update. Still the same problem. Don't worry about it. Get some rest and we can look at this tomorrow..... this is a minor issue.

Quote from fbeye

Stupid question. Now with the inclusion of the "shared" folder, does this make it obsolete in the docker container to add the /path/to/config or will this new way already assume that?

For example, in my Speedtest container, will I still need;

Code

volumes:
            - '/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/container/speedtest:/config'
            - '/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/container/speedtest/web:/etc/ssl/web'

Being my previous setup was using ;

Code

/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/container/

As the container /config directory, the new shared folder said directory already exists, so I made a

Code

/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/container/

Folder.

Display More

I wouldn't think so, since the container is looking for a volume to look at