January 21, 20251 yr 4 minutes ago, primeval_god said: No reboot should be necessary but you do have to run Compose Up after making any changes for them to take effect. I dont think it is required but have you tried running Compose Down and then Compose Up to recreate the stack? Odd, I made sure last night the docker-compose.override.yml files were updated and rebooted the server earlier today after making some zfs changes. However now after doing a down and up the containers are correctly reporting. Apprecaite the help.
January 21, 20251 yr Hi, I am having trouble connecting to my container. I am trying to spin up a WikiJS container as a learning exercise. I copy-pasted the compose file from the official docs (https://docs.requarks.io/install/docker), hit Compose Up, and tried to access on MY_SERVER:33000. I have tried lots of settings with adding networks, trying to connect to the existing bridge network, all without success. My exact compose file is below. What am I doing wrong? Thanks!! services: db: image: postgres:15-alpine environment: POSTGRES_DB: wiki POSTGRES_PASSWORD: wikijsrocks POSTGRES_USER: wikijs logging: driver: "none" restart: unless-stopped volumes: - db-data:/var/lib/postgresql/data wiki: image: ghcr.io/requarks/wiki:2 depends_on: - db environment: DB_TYPE: postgres DB_HOST: db DB_PORT: 5432 DB_USER: wikijs DB_PASS: wikijsrocks DB_NAME: wiki restart: unless-stopped ports: - "33000:80" volumes: db-data: Edited January 21, 20251 yr by acdn01
January 21, 20251 yr Every time I 'Compose Down' a stack the images show up in the Docker tab as 'Orphaned images' I'm new to the compose plugin, but am wondering is there something I can do so that this doesn't happen? I'm not looking to remove them, just to not have UNRAID display them in this way.
January 22, 20251 yr Author 17 hours ago, acdn01 said: Hi, I am having trouble connecting to my container. I am trying to spin up a WikiJS container as a learning exercise. I copy-pasted the compose file from the official docs (https://docs.requarks.io/install/docker), hit Compose Up, and tried to access on MY_SERVER:33000. I have tried lots of settings with adding networks, trying to connect to the existing bridge network, all without success. My exact compose file is below. What am I doing wrong? This thread is for discussing issues with the compose plugin (the ui interface) not specific compose stacks or the intricacies of compose itself. The fact of the matter is I am not a docker compose guru. The only thing i notice about your compose file right off the bat is that it doesnt defined any networks, nor connect any to the containers.
January 22, 20251 yr Right. I'll look through the docker compose docs to try to find a way to get these containers served by Unraid's docker network. I was hoping someone here knew enough to help.
January 23, 20251 yr On 1/22/2025 at 12:26 PM, blender50 said: Every time I 'Compose Down' a stack the images show up in the Docker tab as 'Orphaned images' I'm new to the compose plugin, but am wondering is there something I can do so that this doesn't happen? I'm not looking to remove them, just to not have UNRAID display them in this way. Install the User Scripts plugin. It comes with a script to auto remove orphan images. Set it to run on a schedule and it'll clean it up for you. It's an awesome plugin allowing php and bash scripts to be easily run from the ui.
January 25, 20251 yr I am not looking to 'auto-remove' the images, I was hoping that there would be something I could do so that when the stack is taken down the images would be 'saved' just like a normal docker image from the app store is. That is, when you stop an app store docker app typically the image is saved someplace and no orphan is displayed, and when the docker is brought back online (started) it utilizes the same img as it did previously. Is there not something in the compose file I could add the would 'save' the img like that?
January 26, 20251 yr The equivalent of stopping a CA container would be "compose stop" instead of "compose down" so I guess you could run that in the terminal in the stack's folder instead of using the button.
February 27, 20251 yr Hi everyone, I was a big fan of this plugin but suddenly the docker compose section on the "docker" page in unraid is completly gone. The only thing I changed was trying to apply the immich compose configuration. Also I cannot open the settings page of the plugin. Of course I tried the usual stuff already like reinstalling the plugin and restarting the server. I am using the newest version of the plugin and unraid version 7.0.0. The plugin was working under this unraid version. Does anyone have an idea? Thanks and kind regards Jan
February 27, 20251 yr Author 1 hour ago, JanV said: Hi everyone, I was a big fan of this plugin but suddenly the docker compose section on the "docker" page in unraid is completly gone. The only thing I changed was trying to apply the immich compose configuration. Also I cannot open the settings page of the plugin. Of course I tried the usual stuff already like reinstalling the plugin and restarting the server. I am using the newest version of the plugin and unraid version 7.0.0. The plugin was working under this unraid version. Does anyone have an idea? Thanks and kind regards Jan What is "the immich compose configuration"?
February 28, 20251 yr Thanks for your replay. I think I was a bit unclear about this. I just meant I started a compose file that is supposed to create containers needed for immich https://immich.app/docs/install/docker-compose/
February 28, 20251 yr Hi, so since updating to 7.0 I've had the issue that the compose plugin just doesn't show any stacks at all. My containers are all started but I see no stacks to edit at all. I checked if the docker-compose.yml are in their respective folders in the plugin folder and they are. Reinstalling the plugin or rebooting didn't do the trick. What could be the issue?
March 1, 20251 yr Author On 2/28/2025 at 10:33 AM, unraid_fk34 said: Hi, so since updating to 7.0 I've had the issue that the compose plugin just doesn't show any stacks at all. My containers are all started but I see no stacks to edit at all. I checked if the docker-compose.yml are in their respective folders in the plugin folder and they are. Reinstalling the plugin or rebooting didn't do the trick. What could be the issue? Has the "Compose Project Directory" on the compose setting page been changed?
March 2, 20251 yr 23 hours ago, primeval_god said: Has the "Compose Project Directory" on the compose setting page been changed? Do you mean the setting page when I access "compose" through the Tools tab in the webGUI? Because that gives me a blank page. Or is there another way to access the setting page? (On the Settings tab there is no Compose Icon) Thanks by the way for a great plugin. I really appreciate the work that you put into this for me essential plugin! Edited March 2, 20251 yr by unraid_fk34
March 2, 20251 yr Author 13 minutes ago, unraid_fk34 said: Do you mean the setting page when I access "compose" through the Tools tab in the webGUI? Because that gives me a blank page. ... Or is there another way to access the setting page? (On the Settings tab there is no Compose Icon) I do and it shouldnt. @unraid_fk34 Wait what? The compose setting page should be available via the settings menu. There is nothing available via the Tools page. Edited March 2, 20251 yr by primeval_god
March 2, 20251 yr On 3/2/2025 at 5:26 PM, primeval_god said: I do and it shouldnt. @unraid_fk34 Wait what? The compose setting page should be available via the settings menu. There is nothing available via the Tools page. Okay, after reinstalling the plugin for the 10th time probably it is showing in the Settings Tab again. But still no luck. Blank page when I click on it. Also it is the only plugin displaying this behaviour. So it's not an overall unraid issue I believe. Edited March 4, 20251 yr by unraid_fk34
March 3, 20251 yr I have the same issue. After installing, i click on it within the plugin tab, and it takes me to settings, but the settings page is just blank. Ive tried reinstalling 5-6 times to no avail.
March 5, 20251 yr On 3/3/2025 at 8:17 PM, mrohach said: I have the same issue. After installing, i click on it within the plugin tab, and it takes me to settings, but the settings page is just blank. Ive tried reinstalling 5-6 times to no avail. Docker enabled? No Problems here with 7.0 and Docker Compose Manager.
March 5, 20251 yr On 2/27/2025 at 4:28 PM, primeval_god said: What is "the immich compose configuration"? I will make one using what I'm running. the immich maintiner moved away from unraid CA. WHile Space invader has a nice system setup. It is best to run a postgress DB, redis, and immich. possible machine learnding via sompose. its scattered on the forum.. followign immich: https://immich.app/docs/install/unraid/ compose file: https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml per: https://immich.app/docs/install/docker-compose I will make a post in guides and link it here...
March 5, 20251 yr Here is a working guide to use docker compose and the data to do it... Edited March 5, 20251 yr by bmartino1 Data
March 5, 20251 yr On 2/28/2025 at 9:33 AM, unraid_fk34 said: Hi, so since updating to 7.0 I've had the issue that the compose plugin just doesn't show any stacks at all. My containers are all started but I see no stacks to edit at all. I checked if the docker-compose.yml are in their respective folders in the plugin folder and they are. Reinstalling the plugin or rebooting didn't do the trick. What could be the issue? data should still be in the stack directory if you added the stack and click advance and set the location on disk. under the docker tab do you see the compose add a new stack? if yes, re-added the stack and point it to the folder, and the compose plugin will reload and reread any previous data. This is the first i'm hearing of a upgrade or reboot where compose breaks and the docker web UI is missing. double-check the plugins page and systemlog to make sure compose got installed and didn't error at boot. If you didn't advance and set to a location, the compose files are saved to the flash drive as a default locations and path: /boot/config/plugins/compose.manager/projects
March 6, 20251 yr Anyone suddenly getting errors when trying to update any and all stacks? All stacks have been on my system for years and have updated fine in the past. Here is the compose file for reference: services: gluetun: image: qmcgaw/gluetun:latest container_name: gluetun-update cap_add: - NET_ADMIN volumes: - /mnt/cache/appdata/gluetun:/gluetun command: update -enduser -providers airvpn Edited March 6, 20251 yr by Avsynthe
March 6, 20251 yr 17 hours ago, bmartino1 said: data should still be in the stack directory if you added the stack and click advance and set the location on disk. under the docker tab do you see the compose add a new stack? if yes, re-added the stack and point it to the folder, and the compose plugin will reload and reread any previous data. This is the first i'm hearing of a upgrade or reboot where compose breaks and the docker web UI is missing. double-check the plugins page and systemlog to make sure compose got installed and didn't error at boot. If you didn't advance and set to a location, the compose files are saved to the flash drive as a default locations and path: /boot/config/plugins/compose.manager/projects Thanks for getting back to me. Checking if all the stacks are still in the mentioned path is the first thing I did when this started occurring. Everything is there. But what I got in all of my stack folders are these other weird duplicates. I don't know exactly when they started popping up but they are not part of the daily backup. --- This is how my compose tab looks btw. There is no option for anything like add stacks. Just completely blank: Oh and important to note. All my dockers are running and active. They start up normally after a reboot. Just docker compose manager isn't showing anything. Edited March 6, 20251 yr by unraid_fk34
March 6, 20251 yr hmmm.. Interesting. I've never experienced the stack button missing before... you can call it via termainl? docker compose -d docker composer -it via the termianl targeting the docker compose file... that will atleast docker compose run the docker stack... I believe you have may have flash drive corruption or cached browsed data that may not be fully loading the page. Do a "super refresh" ctrl + r shift + f5 otherwise, I would recommend uninstalling the docker compose and reinstalling the compose plugin from the CA.... I would recommend backing up the docker compose files that you do have and deleting the folder off the flash drive and do a plugin reinstall to regain webui controls back.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.