Another Error 500 while migrating to docker-compose

Sean · 16. Juli 2023

Hi,

I tried to migrate from the "old" omv-extras docker to docker-compose following KM0201's guide https://forum.openmediavault.org/index.php?thread/48003-guide-using-the-new-docker-plugin/ , but in step 11, after entering the new paths and trying to apply the changes, I got this error:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color compose 2>&1' with exit code '1': orion.local:
----------
          ID: docker_install_packages
    Function: pkg.installed
      Result: False
     Comment: Problem encountered installing package(s). Additional info follows:

              errors:
                  - Running scope as unit: run-rf92e55227d6b4ca390754b6cc4f3c819.scope
                    E: Sub-process /usr/bin/dpkg returned an error code (1)
     Started: 15:27:45.906497
    Duration: 46967.524 ms
     Changes:
              ----------
              containerd:
                  ----------
                  new:
                  old:
                      1.4.13~ds1-1~deb11u4
              containerd.io:
                  ----------
                  new:
                      1.6.21-1
                  old:
              docker-ce-cli:
                  ----------
                  new:
                      5:24.0.4-1~debian.11~bullseye
                  old:
              docker.io:
                  ----------
                  new:
                  old:
                      20.10.5+dfsg1-1+deb11u2
              runc:
                  ----------
                  new:
                  old:
                      1.0.0~rc93+ds1-5+deb11u2
----------
          ID: docker_compose_install_packages
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 15:28:32.887698
    Duration: 1598.188 ms
     Changes:
----------
          ID: docker_purged_packages
    Function: pkg.purged
      Result: False
     Comment: Problem encountered removing package(s). Additional info follows:

              errors:
                  - Running scope as unit: run-r2282fc5c8e204c8e8fa5f9787da0341f.scope
                    E: Sub-process /usr/bin/dpkg returned an error code (1)
     Started: 15:28:34.486162
    Duration: 12448.088 ms
     Changes:
              ----------
              installed:
                  ----------
                  docker-compose:
                      ----------
                      new:
                      old:
                          1.25.0-1
              removed:
                  ----------
----------
          ID: configure_compose_global_env_file
    Function: file.managed
        Name: /srv/mergerfs/Data/compose/global.env
      Result: True
     Comment: File /srv/mergerfs/Data/compose/global.env is in the correct state
     Started: 15:28:46.946963
    Duration: 265.331 ms
     Changes:
----------
          ID: /etc/systemd/system/docker.service.d/waitAllMounts.conf
    Function: file.managed
      Result: True
     Comment: File /etc/systemd/system/docker.service.d/waitAllMounts.conf is in the correct state
     Started: 15:28:47.212528
    Duration: 3.11 ms
     Changes:
----------
          ID: systemd_daemon_reload_docker
    Function: cmd.run
        Name: systemctl daemon-reload
      Result: True
     Comment: Command "systemctl daemon-reload" run
     Started: 15:28:47.217266
    Duration: 461.093 ms
     Changes:
              ----------
              pid:
                  94412
              retcode:
                  0
              stderr:
              stdout:
----------
          ID: configure_etc_docker_dir
    Function: file.directory
        Name: /etc/docker
      Result: True
     Comment: The directory /etc/docker is in the correct state
     Started: 15:28:47.678987
    Duration: 3.258 ms
     Changes:
----------
          ID: /etc/docker/daemon.json
    Function: file.serialize
      Result: True
     Comment: File /etc/docker/daemon.json is in the correct state
     Started: 15:28:47.682494
    Duration: 6.626 ms
     Changes:
----------
          ID: docker
    Function: service.running
      Result: False
     Comment: Job for docker.service failed because the control process exited with error code.
              See "systemctl status docker.service" and "journalctl -xe" for details.
     Started: 15:28:47.719754
    Duration: 411.986 ms
     Changes:
----------
          ID: create_usr_local_bin_dir
    Function: file.directory
        Name: /usr/local/bin
      Result: True
     Comment: The directory /usr/local/bin is in the correct state
     Started: 15:28:48.132922
    Duration: 6.682 ms
     Changes:
----------
          ID: /usr/local/bin/docker-compose
    Function: file.symlink
      Result: True
     Comment: Symlink /usr/local/bin/docker-compose is present and owned by root:root
     Started: 15:28:48.140212
    Duration: 30.104 ms
     Changes:
----------
          ID: configure_compose_scheduled_jobs
    Function: file.managed
        Name: /etc/cron.d/omv-compose-backup
      Result: True
     Comment: File /etc/cron.d/omv-compose-backup is in the correct state
     Started: 15:28:48.170926
    Duration: 49.667 ms
     Changes:

Alles anzeigen

Docker shows as installed, but not running in the dashboard (it is activated in the omv-extras setting, though).

Maybe it's a little thing. I looked through some parts of the pinned thread regarding docker-compose, but I couldn't find a solution to this problem. Any ideas?

chente · 16. Juli 2023

Please post a screenshot of the GUI in Services>Compose>Settings

Sean · 16. Juli 2023

Thanks for your reply. I think I found the reason for the error in the OMV-extras documentation: Don't use a mergerfs file system. (Maybe the guide could be extended by one sentence?)

Now I created the shares on another drive, and docker is running. But, unlike to what it says in the guide, my containers are not running. They also don't show if I enter "docker image ls" or "docker images" at the command line...

chente · 16. Juli 2023

Zitat von Sean

Thanks for your reply. I think I found the reason for the error in the OMV-extras documentation: Don't use a mergerfs file system. (Maybe the guide could be extended by one sentence?)

I assume you mean the footnote in this section. https://wiki.omv-extras.org/do…ompose_and_docker_folders What else would you add?

Zitat von Sean

Now I created the shares on another drive, and docker is running. But, unlike to what it says in the guide, my containers are not running. They also don't show if I enter "docker image ls" or "docker images" at the command line...

I don't know the steps followed up to this point, so it's hard to answer.

Sean · 16. Juli 2023

Zitat von chente

I assume you mean the footnote in this section. https://wiki.omv-extras.org/do…ompose_and_docker_folders What else would you add?

No, I was actually referring to the guide I mentioned in my first post. It was actually the wiki page that helped me find the problem, so I don't think it needs any editing.

Zitat

I don't know the steps followed up to this point, so it's hard to answer.

I followed KM0201's guide:

Zitat

1. Log in to OMV and go to Shared Folders.

2. Create a folder called "compose". If this is a new install, create a folder called "containers". This really needs to be on a larger data drive, as these folders can get large. If you are setting up for the first time, you'll also need the absolute path to this folder (click the 4 squares in the upper right, put a check next to absolute path). Click the copy icon at the end of this path and just save it in a text file for now.

3. In the webUI, Go to System/omv-extras

4. Click Enable Docker Repo (if it's not already)

5. Save/Apply

6. Click apt-clean

7. Once apt finishes, go to System/Plugins

8. Do a search for "compose" and install the openmediavault-compose plugin.

9. Now with the installation of the compose plugin, go to Services/Compose/Settings.

10. In the drop down box at the top, set that to the compose folder we created in Step 2.

11. In the "docker storage" path... If it is anything other than the path you recorded earlier, paste your path there. If it already has your path there, then there's no need to make a change. If it's a new install, paste the path you recorded earlier to the "containers" folder we created.

12. Click Save

13. CLICK RESTART DOCKER (this is important)

After docker starts and says it is installed and running.. If you had a previous installation, all of your containers, etc.. should be up and running as they always were and you can continue to use docker the way you always have.

Alles anzeigen

And that last sentence just doesn't hold for me. I can't find any containers.

ryecoaaron · 16. Juli 2023

Zitat von Sean

I can't find any containers.

Did you use the same docker storage path as you did when you created the containers? When you install the compose plugin, it should default to the current docker storage path if you have docker installed.

Sean · 16. Juli 2023

Zitat von ryecoaaron

Did you use the same docker storage path as you did when you created the containers? When you install the compose plugin, it should default to the current docker storage path if you have docker installed.

Ah, that did the trick. I was kind of wondering how the containers can run if the docker directory changes. OK, thanks for your help, and I'll post again here if I encounter any more trouble while migrating the containers.

chente · 16. Juli 2023

Zitat von Sean

I'll post again here if I encounter any more trouble while migrating the containers.

This can also help you. https://wiki.omv-extras.org/do…openmediavault-compose_67

Sean · 16. Juli 2023

Hmm, whenever I use the configuration file from portainer to create a new "file" in Compose and then press "up", I get:

Zitat

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/docker/compose/transmission/transmission.yml' --env-file '/docker/compose/transmission/transmission.env' --env-file '/docker/compose/global.env' up -d 2>&1': Define and run multi-container applications with Docker.

Usage:

docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]

docker-compose -h|--help

Options:

-f, --file FILE Specify an alternate compose file

(default: docker-compose.yml)

-p, --project-name NAME Specify an alternate project name

(default: directory name)

--verbose Show more output

--log-level LEVEL Set log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)

--no-ansi Do not print ANSI control characters

-v, --version Print version and exit

-H, --host HOST Daemon socket to connect to

--tls Use TLS; implied by --tlsverify

--tlscacert CA_PATH Trust certs signed only by this CA

--tlscert CLIENT_CERT_PATH Path to TLS certificate file

--tlskey TLS_KEY_PATH Path to TLS key file

--tlsverify Use TLS and verify the remote

--skip-hostname-check Don't check the daemon's hostname against the

name specified in the client certificate

--project-directory PATH Specify an alternate working directory

(default: the path of the Compose file)

--compatibility If set, Compose will attempt to convert keys

in v3 files to their non-Swarm equivalent

--env-file PATH Specify an alternate environment file

Commands:

build Build or rebuild services

bundle Generate a Docker bundle from the Compose file

config Validate and view the Compose file

create Create services

down Stop and remove containers, networks, images, and volumes

events Receive real time events from containers

exec Execute a command in a running container

help Get help on a command

images List images

kill Kill containers

logs View output from containers

pause Pause services

port Print the public port for a port binding

ps List containers

pull Pull service images

push Push service images

restart Restart services

rm Remove stopped containers

run Run a one-off command

scale Set number of containers for a service

start Start services

stop Stop services

top Display the running processes

unpause Unpause services

up Create and start containers

version Show the Docker-Compose version information

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/docker/compose/transmission/transmission.yml' --env-file '/docker/compose/transmission/transmission.env' --env-file '/docker/compose/global.env' up -d 2>&1': Define and run multi-container applications with Docker.

Usage:

docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]

docker-compose -h|--help

Options:

-f, --file FILE Specify an alternate compose file

(default: docker-compose.yml)

-p, --project-name NAME Specify an alternate project name

(default: directory name)

--verbose Show more output

--log-level LEVEL Set log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)

--no-ansi Do not print ANSI control characters

-v, --version Print version and exit

-H, --host HOST Daemon socket to connect to

--tls Use TLS; implied by --tlsverify

--tlscacert CA_PATH Trust certs signed only by this CA

--tlscert CLIENT_CERT_PATH Path to TLS certificate file

--tlskey TLS_KEY_PATH Path to TLS key file

--tlsverify Use TLS and verify the remote

--skip-hostname-check Don't check the daemon's hostname against the

name specified in the client certificate

--project-directory PATH Specify an alternate working directory

(default: the path of the Compose file)

--compatibility If set, Compose will attempt to convert keys

in v3 files to their non-Swarm equivalent

--env-file PATH Specify an alternate environment file

Commands:

build Build or rebuild services

bundle Generate a Docker bundle from the Compose file

config Validate and view the Compose file

create Create services

down Stop and remove containers, networks, images, and volumes

events Receive real time events from containers

exec Execute a command in a running container

help Get help on a command

images List images

kill Kill containers

logs View output from containers

pause Pause services

port Print the public port for a port binding

ps List containers

pull Pull service images

push Push service images

restart Restart services

rm Remove stopped containers

run Run a one-off command

scale Set number of containers for a service

start Start services

stop Stop services

top Display the running processes

unpause Unpause services

up Create and start containers

version Show the Docker-Compose version information in /usr/share/openmediavault/engined/rpc/compose.inc:605

Stack trace:

#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatusgp...', '/tmp/bgoutputlm...')

#1 /usr/share/openmediavault/engined/rpc/compose.inc(608): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)

#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)

#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)

#6 {main}

Alles anzeigen

Here's the file:

Code

version: "2"
services:
  transmission:
    image: linuxserver/transmission
    container_name: transmission
    environment:
      - PUID=1006
      - PGID=100
      - TZ=Europe/Paris
    volumes:
      - /home/focker/transmission:/config
      - /srv/mergerfs/Data/Media/News:/downloads
      - /srv/mergerfs/Data/Public/torrents:/watch
    ports:
      - 9091:9091
      - 51413:51413
      - 51413:51413/udp
    restart: always

Alles anzeigen

chente · 16. Juli 2023

Zitat von Sean

Hmm, whenever I use the configuration file from portainer to create a new "file" in Compose and then press "up", I get:

Have you stopped and removed the container in Portainer previously?

Sean · 16. Juli 2023

I removed the stack, but not the container. Do I need to remove both?

ryecoaaron · 16. Juli 2023

Zitat von Sean

Do I need to remove both?

Why not? Since it doesn't remove the persistent volumes, that shouldn't be a big deal. What version of docker and docker-compose is installed? The Settings tab tells you.

Sean · 17. Juli 2023

No change. Even without the container, I get the same error.

One thing that puzzles me about the error message: When a command includes the command syntax in the error message, that usually means there is a syntax error in the command line. Could this be the case here?

ryecoaaron · 17. Juli 2023

Zitat von Sean

When a command includes the command syntax in the error message, that usually means there is a syntax error in the command line. Could this be the case here?

It is if you have an incompatible version of docker and/or docker-compose installed on your system. I am using the plugin myself and it works fine for the expected version of docker and docker-compose. That is why I asked what version you had installed on your system.

Sean · 17. Juli 2023

Sorry, I overlooked that question.

Docker: docker.io 20.10.5+dfsg1-1+deb11u2

Compose: docker-compose 1.25.0-1

ryecoaaron · 17. Juli 2023

I guess I can't allow docker.io from the Debian repos anymore. This means i386 will no longer be supported. Is your system i386? dpkg --print-architecture

Sean · 17. Juli 2023

No, it's amd64

Sean · 17. Juli 2023

Just in case I made a mistake during the setup, here's a screenshot of the settings tab.

Edit: Since all my data disks form one mergerfs volume which I can't use for the compose files, I chose a location on the system disk for the "shared folder".

ryecoaaron · 17. Juli 2023

If it is amd64, then you didn't enable the docker repo in omv-extras because your system has docker from the Debian repo installed. Enable the docker repo in omv-extras and then post the output of:

sudo omv-salt deploy run compose

Sean · 17. Juli 2023

In my defence... docker was activated, but the command you posted did the trick; it's working now.

Thanks for your help!

For the sake of completeness, here's the output:

Code

orion.local:
----------
          ID: docker_install_packages
    Function: pkg.installed
      Result: True
     Comment: The following packages were installed/updated: docker-ce
     Started: 16:53:58.672421
    Duration: 62334.203 ms
     Changes:
              ----------
              containerd:
                  ----------
                  new:
                  old:
                      1.4.13~ds1-1~deb11u4
              containerd.io:
                  ----------
                  new:
                      1.6.21-1
                  old:
              docker-ce:
                  ----------
                  new:
                      5:24.0.4-1~debian.11~bullseye
                  old:
              docker-ce-cli:
                  ----------
                  new:
                      5:24.0.4-1~debian.11~bullseye
                  old:
              docker.io:
                  ----------
                  new:
                  old:
                      20.10.5+dfsg1-1+deb11u2
              runc:
                  ----------
                  new:
                  old:
                      1.0.0~rc93+ds1-5+deb11u2
----------
          ID: docker_compose_install_packages
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 16:55:01.038773
    Duration: 1895.405 ms
     Changes:
----------
          ID: docker_purged_packages
    Function: pkg.purged
      Result: True
     Comment: All targeted packages were purged.
     Started: 16:55:02.934458
    Duration: 11691.376 ms
     Changes:
              ----------
              installed:
                  ----------
                  docker-compose:
                      ----------
                      new:
                      old:
                          1.25.0-1
              removed:
                  ----------
----------
          ID: configure_compose_dir_transmission
    Function: file.directory
        Name: /docker/compose/transmission
      Result: True
     Comment: The directory /docker/compose/transmission is in the correct state
     Started: 16:55:14.641524
    Duration: 16.792 ms
     Changes:
----------
          ID: configure_compose_transmission_file
    Function: file.managed
        Name: /docker/compose/transmission/transmission.yml
      Result: True
     Comment: File /docker/compose/transmission/transmission.yml is in the correct state
     Started: 16:55:14.658903
    Duration: 211.958 ms
     Changes:
----------
          ID: configure_compose_env_transmission_file
    Function: file.managed
        Name: /docker/compose/transmission/transmission.env
      Result: True
     Comment: File /docker/compose/transmission/transmission.env is in the correct state
     Started: 16:55:14.871120
    Duration: 16.195 ms
     Changes:
----------
          ID: configure_compose_global_env_file
    Function: file.managed
        Name: /docker/compose/global.env
      Result: True
     Comment: File /docker/compose/global.env is in the correct state
     Started: 16:55:14.887609
    Duration: 15.068 ms
     Changes:
----------
          ID: /etc/systemd/system/docker.service.d/waitAllMounts.conf
    Function: file.managed
      Result: True
     Comment: File /etc/systemd/system/docker.service.d/waitAllMounts.conf is in the correct state
     Started: 16:55:14.902919
    Duration: 3.125 ms
     Changes:
----------
          ID: systemd_daemon_reload_docker
    Function: cmd.run
        Name: systemctl daemon-reload
      Result: True
     Comment: Command "systemctl daemon-reload" run
     Started: 16:55:14.908511
    Duration: 516.866 ms
     Changes:
              ----------
              pid:
                  342367
              retcode:
                  0
              stderr:
              stdout:
----------
          ID: configure_etc_docker_dir
    Function: file.directory
        Name: /etc/docker
      Result: True
     Comment: The directory /etc/docker is in the correct state
     Started: 16:55:15.425912
    Duration: 3.046 ms
     Changes:
----------
          ID: /etc/docker/daemon.json
    Function: file.serialize
      Result: True
     Comment: File /etc/docker/daemon.json is in the correct state
     Started: 16:55:15.429276
    Duration: 292.367 ms
     Changes:
----------
          ID: docker
    Function: service.running
      Result: True
     Comment: The service docker is already running
     Started: 16:55:15.783060
    Duration: 97.113 ms
     Changes:
----------
          ID: create_usr_local_bin_dir
    Function: file.directory
        Name: /usr/local/bin
      Result: True
     Comment: The directory /usr/local/bin is in the correct state
     Started: 16:55:15.880746
    Duration: 3.173 ms
     Changes:
----------
          ID: /usr/local/bin/docker-compose
    Function: file.symlink
      Result: True
     Comment: Symlink /usr/local/bin/docker-compose is present and owned by root:root
     Started: 16:55:15.884226
    Duration: 33.413 ms
     Changes:
----------
          ID: configure_compose_scheduled_jobs
    Function: file.managed
        Name: /etc/cron.d/omv-compose-backup
      Result: True
     Comment: File /etc/cron.d/omv-compose-backup is in the correct state
     Started: 16:55:15.918262
    Duration: 49.955 ms
     Changes:

Summary for orion.local
-------------
Succeeded: 15 (changed=3)
Failed:     0
-------------
Total states run:     15
Total run time:   77.180 s

Alles anzeigen

Another Error 500 while migrating to docker-compose

Jetzt mitmachen!

Tags