11 minutes ago, primeval_god said:

Plans yes, but I have not had time to setup a test machine and address the PHP changes. 

It may be more convenient to set this up in a VM as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

4 hours ago, Squid said:

Quick glance shows that it works on 6.12?  I don't use this, but what am I missing?

Some things don't, e.g. if you "Edit Stack" and choose "UI labels" the relevant page doesn't open. 

On 3/22/2023 at 1:44 PM, Kilrah said:

Some things don't, e.g. if you "Edit Stack" and choose "UI labels" the relevant page doesn't open. 

This, and also I am having a weird issue where I uninstalled the plugin, but when I try to reinstall it it says it's already installed

 

plugin: installing: compose.manager.plg
Executing hook script: pre_plugin_checks
plugin: downloading: compose.manager.plg ... done

Executing hook script: pre_plugin_checks

+==============================================================================
| Skipping package compose.manager-package-2022.11.17 (already installed)
+==============================================================================


----------------------------------------------------
Applying WebUI Patches...
----------------------------------------------------

plugin: run failed: /bin/bash
Executing hook script: post_plugin_checks

 

Just wanted to drop by and say thanks for this, it's really useful!

Ran into an issue that I'm not sure if it's on my end.

Issue: Web UI URL's are not updating

Use case:
I have folders with the docker-compose.yml files and I use the "Advanced > Stack Directory" setting to link to the yml file.

I add the UI Labels to the docker-compose.yml file, like this:

    labels:
      net.unraid.docker.icon: "https://raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/jdownloader-2-icon.png"    
      net.unraid.docker.webui: "http://dl.mydomain.com"

 

Detail:
When I have an existing stack, if I update the "net.unraid.docker.webui", the webui link on the "docker" page doesn't update.

This happens even when I click "edit stack" > "UI Labels" and "save".  (It is pulling the correct info from the .yml file)

Checks I have done:
-When I check the plugin folder, /boot/config/plugins/compose.manager/projects/ the .yml file is correct and the url's are correct
-I tried logging in with "incognito" mode to see if it was cached or a cookie.  No change

-I checked the unraid dockerMan/templates-user dir and there is no .xml file for the docker I'm using

-Delete stack & recreate

(Have not tried rebooting)

 

So, I'm not sure where it's pulling the web ui url from, any other tips on where I should look?

P.s.  I'm also using the docker folders plugin.  Not sure if that's what is caching the old URL somewhere.  Didn't see anything in the plugin dir files.
P.p.s I'm only changing the URL from https to http

 

2 hours ago, samsausages said:

Ran into an issue that I'm not sure if it's on my end.

Issue: Web UI URL's are not updating

Its a known issue. The unRAID webui allows specifying webui and icons via labels but then caches them and doesnt update them when the labels change. I think somewhere further back in this thread someone mentioned being able to locate and delete the files the UI is using to cache the values.

1 hour ago, primeval_god said:

Its a known issue. The unRAID webui allows specifying webui and icons via labels but then caches them and doesnt update them when the labels change. I think somewhere further back in this thread someone mentioned being able to locate and delete the files the UI is using to cache the values.

OK, thanks for confirming!  Now I know what to search for.
Cheers!

the current version in unraid of docker compose is 2.11.2 are there any plans to update to 2.17.2? this depends on this plugins or unraid?

 

when in a docker compose file says "version: "3"" is this related with the docker compose version supported or with this?

https://docs.docker.com/compose/compose-file/compose-file-v3/

Or what should I use as default? 3.8? 3.9?

6 hours ago, L0rdRaiden said:

the current version in unraid of docker compose is 2.11.2 are there any plans to update to 2.17.2? this depends on this plugins or unraid?

Yes an update to this plugin is planned, but no eta.

 

6 hours ago, L0rdRaiden said:

when in a docker compose file says "version: "3"" is this related with the docker compose version supported or with this?

https://docs.docker.com/compose/compose-file/compose-file-v3/

Yes, however I believe the current recommendation is to not include the version line in compose files unless you have a reason to restrict the file to a specific compose file version.

 

https://docs.docker.com/compose/compose-file/04-version-and-name/

Edited April 12, 20233 yr by primeval_god

Where are Volumes stored? For example, this is declared by the Immich docker compose stack. If left as is and bind mounts are not declared, where would the pgdata volume be stored in the unraid system? 

 

volumes:
  pgdata:
  model-cache:
  tsdata:

 

They would get lost in the Docker image.

Stacks should be adapted to unraid, that includes replacing any volumes with appropriate mounts.

On 4/12/2023 at 3:15 PM, primeval_god said:

Yes an update to this plugin is planned, but no eta.

 

Can I ask about release cadence. Compose is now 13 versions out of date, is there any way we can assist in increasing this cadence?

 

Does the addon need work every time the compose dependency changes? If so can we split this into two addons, one for compose itself and one for manager? Could we request compose be shipped with unRAID itself, would that help?

 

Trying to understand where the bottleneck is as we just passed the 200 days mark since the shipped version of compose was released and that is too long.

 

This post is not a criticism at all, just a realistic shout out to see if we can find a way to make this burden easier for you.

6 hours ago, NAS said:

Does the addon need work every time the compose dependency changes?

Generally no, right now it needs work for unRAID 6.12.0 compatibility.

 

6 hours ago, NAS said:

If so can we split this into two addons, one for compose itself and one for manager?

If you would like to fork the plugin go ahead, but i have no use for compose on unRAID without a web-ui component and i am not keen on maintain such a thing.

 

6 hours ago, NAS said:

Could we request compose be shipped with unRAID itself, would that help?

You can try, the only reason this plugin exists is because unRAID does not provide official compose support.

 

6 hours ago, NAS said:

Trying to understand where the bottleneck is as we just passed the 200 days mark since the shipped version of compose was released and that is too long.

 The main reason for no recent updates to the underlying compose version is because no one has brought it up and i havent thought about it in some time. 

Could we trigger an update on a semi regular basis? I do not know what your build pipeline is but I would like to avoid getting into a situation where we are essentially nagging you as a trigger.

 

Even once a month or perhaps on each minor release could be automated.?

 

Ultimately the end goal should be to make your life easier helping where we can; forking, splitting effort or taking away from your work should never be our goal.

Can anyone help me with  this docker compose?

I have my dockers in general with a fixed IP on my network in the internface br1, I use macvlan

This is my typical network config

 

 

 

 

So I want nextcloud to have a fixed IP in my network and communicate with the other dockers, redis, mariadb, over an internal docker network no published in my network.

 

This is my coked compose file, but I'm not sure how to configure the network part, or what is the purpose of the volumen parameter at the beginning. I would appreciate any help or any other improvement you might see.

 

version: '3.3'

volumes:
  Nextcloud:  #volumen a la izquierda de los :
  Media:
  mariadb:
  redis:

networks:
  br1:
    external: true
  nextcloud_network:
    driver: bridge

services:
  db:
    image: mariadb:10.6
    restart: unless-stopped
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    volumes:
      - /mnt/user/Docker/Nextcloud/mariadb:/var/lib/mysql
    environment:
      - TZ=Europe/Paris
      - MYSQL_ROOT_PASSWORD=random_msql_root_password
      - MYSQL_PASSWORD=must_match_1
      - MYSQL_DATABASE=must_match_2
      - MYSQL_USER=must_match_3
      - MARIADB_AUTO_UPGRADE=1
      - MARIADB_DISABLE_UPGRADE_BACKUP=1
    networks:
      - nextcloud_network
    dns:
      - 10.10.40.5    
    labels:
      - "com.centurylinklabs.watchtower.enable=true"


  redis:
    image: redis:alpine
    restart: unless-stopped
    command: redis-server --requirepass someredispassword
    volumes:
      - /mnt/user/Docker/Nextcloud/redis:/data
    networks:
      - nextcloud_network
    dns:
      - 10.10.40.5
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

  nextcloud:
    image: nextcloud:apache
    restart: unless-stopped
    depends_on:
      - db
      - redis
    volumes:
      - /mnt/user/Docker/Nextcloud:/var/www/html
      - /mnt/user/Media:/var/www/html/data
      - type: tmpfs
        target: /tmp
    environment:
      - TZ=Europe/Paris
      - PUID=99
      - PGID=100
      - UMASK=022
      - MYSQL_PASSWORD=must_match_1
      - MYSQL_DATABASE=must_match_2
      - MYSQL_USER=must_match_3
      - MYSQL_HOST=db
      - REDIS_HOST=redis
      - REDIS_HOST_PASSWORD=someredispassword
    networks:
      nextcloud_network:
      br1:
        ipv4_address: 10.10.40.160
    ports:
      - 8080:80
    dns:
      - 10.10.40.5
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

 

Edited April 19, 20233 yr by L0rdRaiden

You can just remove the volume section as it serves no purpose on unRAID when you are using bind mounts to the app data folder for all your volumes. I dont know much about macvlan networking, the only thing strange i see networking wise in your compose file is the ports specifier under nextcloud. I believe ports is only used to create a host port mapping on a bridge type network. If you are using macvlan i dont think the ports serves a purpose as all the container ports are exposed directly on its assigned ip address.

Any idea why I'm getting this error when I do compose UP or DOWN?

 

Apr 20 16:20:00 Unraid nginx: 2023/04/20 16:20:00 [error] 18251#18251: *4620476 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 10.10.10.23, server: 10-10-10-5.e0eacb8df486bfb2253b8048c08468d2ab8ec813.myunraid.net, request: "GET /logterminal/compose_manager_action/token HTTP/2.0", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/token", host: "10-10-10-5.e0eacb8df486bfb2253b8048c08468d2ab8ec813.myunraid.net", referrer: "https://10-10-10-5.e0eacb8df486bfb2253b8048c08468d2ab8ec813.myunraid.net/logterminal/compose_manager_action/"
Apr 20 16:20:01 Unraid nginx: 2023/04/20 16:20:01 [error] 18251#18251: *4620590 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 10.10.10.23, server: 10-10-10-5.e0eacb8df486bfb2253b8048c08468d2ab8ec813.myunraid.net, request: "GET /logterminal/compose_manager_action/ws HTTP/1.1", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/ws", host: "10-10-10-5.e0eacb8df486bfb2253b8048c08468d2ab8ec813.myunraid.net"

 

version: '3.8'

networks:
  br1:
    external: true
  nextcloud_network:
    driver: bridge

services:

  mariadb:
    image: mariadb:10.6
    container_name: MariaDBNC
    restart: unless-stopped
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    healthcheck:
      test: ["CMD-SHELL", "mysql nextcloud -unextcloud -psssssssssssss -e 'SELECT 1;'  || exit 1"]
      interval: 2s
      retries: 120
    volumes:
      - /mnt/user/Docker/Nextcloud/mariadb:/var/lib/mysql
    environment:
      - TZ=Europe/Madrid
      - MYSQL_ROOT_PASSWORD=sssssssssssssss
      - MYSQL_PASSWORD=sssssssssssssssss
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MARIADB_AUTO_UPGRADE=1
      - MARIADB_DISABLE_UPGRADE_BACKUP=1
    networks:
      - nextcloud_network
    dns:
      - 10.10.40.5    
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

  redis:
    image: redis:alpine
    container_name: RedisNC
    restart: unless-stopped
    command: redis-server --requirepass ssssssssssssssssssss
    volumes:
      - /mnt/user/Docker/Nextcloud/redis:/data
    environment:
      - TZ=Europe/Madrid
      - PUID=1000
      - PGID=100
    networks:
      - nextcloud_network
    dns:
      - 10.10.40.5
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

  nextcloud:
    image: nextcloud:apache
    container_name: Nextcloud
    restart: unless-stopped
    depends_on:
      mariadb:
        condition: service_healthy
    volumes:
      - /mnt/user/Docker/Nextcloud/nextcloud:/var/www/html
      - /mnt/user/Media/Nextcloud:/var/www/html/data
      - type: tmpfs
        target: /tmp
        tmpfs:
          size: 1000000000
    environment:
      - TZ=Europe/Madrid
      - PUID=1000
      - PGID=100
      - UMASK=022
      - MYSQL_PASSWORD=sssssssssssssssss
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=mariadb
      - REDIS_HOST=redis
      - REDIS_HOST_PASSWORD=sssssssssssss
    networks:
      nextcloud_network:
      br1:
        ipv4_address: 10.10.40.160
    dns:
      - 10.10.40.5
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

 

Another issue I have is that the first time I put the WebUI label I did http://[IP]:[PORT:443]/ by mistake, I have changed it to http://[IP]:[PORT:80]/ and http://[IP] but I still get this in the webui

 

 

Thanks in advance

Edited April 20, 20233 yr by L0rdRaiden

On 4/17/2023 at 3:28 AM, NAS said:

Could we trigger an update on a semi regular basis? I do not know what your build pipeline is but I would like to avoid getting into a situation where we are essentially nagging you as a trigger.

 

Even once a month or perhaps on each minor release could be automated.?

 

Ultimately the end goal should be to make your life easier helping where we can; forking, splitting effort or taking away from your work should never be our goal.

 

 

This works well enough

https://forums.unraid.net/topic/114415-plugin-docker-compose-manager/?do=findComment&comment=1240504

4 hours ago, Presjar said:

This works well enough

https://forums.unraid.net/topic/114415-plugin-docker-compose-manager/?do=findComment&comment=1240504

 

That is for updating containers. The previous poster was asking for the docker compose binary to be updated. It is pretty out of date right now. The plugin is 2.11.2 but the current release is 2.17.3. It is 15 versions older, which will be a huge version jump when it finally upgrades.

Edited April 22, 20233 yr by hasown

On 4/22/2023 at 6:22 PM, hasown said:

That is for updating containers.

 Oh I see.

 

#!/bin/bash
COMPOSE_VERSION=$(curl -s https://api.github.com/repos/docker/compose/releases/latest | grep 'tag_name' | cut -d\" -f4)
curl -L "https://github.com/docker/compose/releases/download/${COMPOSE_VERSION}/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/lib/docker/cli-plugins/docker-compose
sudo chmod +x /usr/local/lib/docker/cli-plugins/docker-compose

Use this as an automatic weekly script until the git is updated more often.

Can some with experience in docker compose help me with this?

 

 It's related with this docker compose

 

###############################################################
# Nextcloud
###############################################################

version: '3.8'

# Networks ####################################################

networks:
  br1:
    driver: macvlan
    external: true
  nextcloud_network:
    internal: true

# Services ####################################################

services:

  mariadb:
    image: mariadb:10.6
    container_name: MariaDBNC
    restart: unless-stopped
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    healthcheck:
      test: ["CMD-SHELL", "mysql nextcloud -u$MYSQL_USER -p$MYSQL_PASSWORD -e 'SELECT 1;'  || exit 1"]
      interval: 2s
      retries: 120
    volumes:
      - /mnt/user/Docker/Nextcloud/mariadb:/var/lib/mysql
    environment:
      - TZ
      - PUID
      - PGID
      - MYSQL_ROOT_PASSWORD
      - MYSQL_PASSWORD
      - MYSQL_DATABASE
      - MYSQL_USER
      - MARIADB_AUTO_UPGRADE=1
      - MARIADB_DISABLE_UPGRADE_BACKUP=1
    networks:
      - nextcloud_network 
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

  redis:
    image: redis:alpine
    container_name: RedisNC
    restart: unless-stopped
    command: redis-server --requirepass $REDIS_HOST_PASSWORD
    volumes:
      - /mnt/user/Docker/Nextcloud/redis:/data
    environment:
      - TZ
      - PUID
      - PGID
    networks:
      - nextcloud_network
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

  app:
    image: nextcloud:fpm-alpine
    container_name: Nextcloud
    restart: unless-stopped
    depends_on:
      mariadb:
        condition: service_healthy
    volumes:
      - /mnt/user/Docker/Nextcloud/nextcloud:/var/www/html
      - /mnt/user/Docker/Nextcloud/nextcloud/config:/var/www/html/config
      - /mnt/user/Media/Nextcloud:/var/www/html/data
      - type: tmpfs
        target: /tmp
        tmpfs:
          size: 1000000000
    environment:
      - TZ
      - PUID
      - PGID
      - MYSQL_PASSWORD
      - MYSQL_DATABASE
      - MYSQL_USER
      - MYSQL_HOST=mariadb
      - REDIS_HOST=redis
      - REDIS_HOST_PASSWORD
    networks:
      - nextcloud_network
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

  web:
    build: ./web
    container_name: Nginx-fpm
    restart: always
    networks:
      nextcloud_network:
      br1:
        ipv4_address: 10.10.40.160
    ports:
      - 8080:80
    volumes:
      - /mnt/user/Docker/Nextcloud/nextcloud:/var/www/html:ro
    environment:
      - TZ
      - PUID
      - PGID
    depends_on:
      - app

  cron:
    image: nextcloud:fpm-alpine
    container_name: CronNC
    restart: unless-stopped
    depends_on:
      - mariadb
      - redis
    volumes:
      - /mnt/user/Docker/Nextcloud/nextcloud:/var/www/html
    environment:
      - TZ
      - PUID
      - PGID
    networks:
      - nextcloud_network
    entrypoint: /cron.sh
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

 

Edited April 24, 20233 yr by L0rdRaiden

I'm trying to update the dokcers in the compose above using watchtower but when It tries I get this error

The container has access to internet so I can't really figure out what the problem is

 

time="2023-04-25T01:01:10+02:00" level=warning msg="Could not do a head request for \"nextcloud:fpm-alpine\", falling back to regular pull." container=/Nextcloud image="nextcloud:fpm-alpine"
time="2023-04-25T01:01:10+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/Nextcloud image="nextcloud:fpm-alpine"
time="2023-04-25T01:01:20+02:00" level=info msg="Unable to update container \"/Nextcloud\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."
time="2023-04-25T01:01:30+02:00" level=warning msg="Could not do a head request for \"nextcloud:fpm-alpine\", falling back to regular pull." container=/CronNC image="nextcloud:fpm-alpine"
time="2023-04-25T01:01:30+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/CronNC image="nextcloud:fpm-alpine"
time="2023-04-25T01:01:40+02:00" level=info msg="Unable to update container \"/CronNC\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."
time="2023-04-25T01:01:50+02:00" level=warning msg="Could not do a head request for \"mariadb:10.6\", falling back to regular pull." container=/MariaDBNC image="mariadb:10.6"
time="2023-04-25T01:01:50+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/MariaDBNC image="mariadb:10.6"
time="2023-04-25T01:02:00+02:00" level=info msg="Unable to update container \"/MariaDBNC\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."
time="2023-04-25T01:02:10+02:00" level=warning msg="Could not do a head request for \"redis:alpine\", falling back to regular pull." container=/RedisNC image="redis:alpine"
time="2023-04-25T01:02:10+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/RedisNC image="redis:alpine"
time="2023-04-25T01:02:20+02:00" level=info msg="Unable to update container \"/RedisNC\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."
time="2023-04-25T01:02:20+02:00" level=info msg="Session done" Failed=0 Scanned=4 Updated=0 notify=no
time="2023-04-25T02:01:10+02:00" level=warning msg="Could not do a head request for \"nextcloud:fpm-alpine\", falling back to regular pull." container=/Nextcloud image="nextcloud:fpm-alpine"
time="2023-04-25T02:01:10+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/Nextcloud image="nextcloud:fpm-alpine"
time="2023-04-25T02:01:20+02:00" level=info msg="Unable to update container \"/Nextcloud\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."
time="2023-04-25T02:01:30+02:00" level=warning msg="Could not do a head request for \"nextcloud:fpm-alpine\", falling back to regular pull." container=/CronNC image="nextcloud:fpm-alpine"
time="2023-04-25T02:01:30+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/CronNC image="nextcloud:fpm-alpine"
time="2023-04-25T02:01:40+02:00" level=info msg="Unable to update container \"/CronNC\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."
time="2023-04-25T02:01:50+02:00" level=warning msg="Could not do a head request for \"mariadb:10.6\", falling back to regular pull." container=/MariaDBNC image="mariadb:10.6"
time="2023-04-25T02:01:50+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/MariaDBNC image="mariadb:10.6"
time="2023-04-25T02:02:00+02:00" level=info msg="Unable to update container \"/MariaDBNC\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."
time="2023-04-25T02:02:10+02:00" level=warning msg="Could not do a head request for \"redis:alpine\", falling back to regular pull." container=/RedisNC image="redis:alpine"
time="2023-04-25T02:02:10+02:00" level=warning msg="Reason: Get \"https://index.docker.io/v2/\": net/http: TLS handshake timeout" container=/RedisNC image="redis:alpine"
time="2023-04-25T02:02:20+02:00" level=info msg="Unable to update container \"/RedisNC\": Error response from daemon: Get \"https://registry-1.docker.io/v2/\": net/http: TLS handshake timeout. Proceeding to next."

 

If I try to access to the url https://registry-1.docker.io/v2/

I get this

 

my script to update compose with user scripts and cron jobs.

 

Any feedback for improvement is welcome, I will improve it.

 

#!/bin/bash

# Define the root directory to search for projects
projects_dir="/boot/config/plugins/compose.manager/projects"

# Find all subdirectories containing docker-compose files
compose_files=$(find "$projects_dir" -maxdepth 2 -name "docker-compose.y*ml")

# Loop over each file found
for file in $compose_files; do
  # Get the directory containing the file
  dir="$(dirname "$file")"

  # Get the last folder name in the directory path
  project_name="$(basename "$dir")"

  # Change the current directory to the project directory
  pushd "$dir"

  # Check if there are any updates available for the Docker images
  if [[ $(docker-compose pull 2>&1) =~ 'Downloaded newer image' ]]; then
    # Get the names of the updated Docker images
    updated_images=$(docker-compose images --quiet | xargs docker inspect --format '{{.RepoTags}}' | tr -d '[] ' | sed 's/,/\n/g')

    # Stop any running containers associated with the project
    docker-compose down

    # Pull the latest version of the Docker images
    docker-compose pull

    # Start the containers in detached mode
    docker-compose up -d --remove-orphans

    # Clean up any unused Docker images
    docker image prune -f

    # Output a notification with the names of the updated Docker images
    echo "Updates available for project $project_name"
    echo "Updated Docker images:"
    echo "$updated_images"
    /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Docker Compose Updates" -d "$project_name updated the images $updated_images" -i "normal"

  else
    echo "No updates available for project $project_name"
    /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Docker Compose Updates" -d "$project_name no updates available" -i "normal"

  fi

  # Change back to the original directory
  popd
done

 

Thank you for the update to `Docker Compose version v2.17.3`. The fix for pull screen glitches is a welcome fix.

I get this errors with Unnraid 6.12 rc5

 

May  2 23:53:53 Unraid nginx: 2023/05/02 23:53:53 [error] 5229#5229: *215414 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 10.10.10.21, server: 10-10-11-5.e0eacb8sdasdasd0846d2ab8ec813.myunraid.net, request: "GET /logterminal/compose_manager_action/ HTTP/2.0", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/", host: "10-10-10-5.e0eacb8df486sdfsdfb8048csdasd68d2ab8ec813.myunraid.net", referrer: "https://10-10-10-5.e0efsdfsdfsb8048c0asdas8d2ab8ec813.myunraid.net/webterminal/syslog/"