primeval_god Posted September 17 Author Posted September 17 6 hours ago, Dal said: Hi. How can I get the networks to display the correct name? You cant. It is a limitation of the way unRAID's Dockerman displays networks. It will hopefully be fixed in a coming release of unRAID. 1 Quote
primeval_god Posted September 17 Author Posted September 17 6 hours ago, Dal said: How do I get Icons to display? I have downloaded a .png file and placed it a folder called icons. The folder is placed in the same directory as the docker-compose.yml and .env file. The icon label is typically a web address, i am not sure if unRAID supports specifying local icons. If it does the path would certainly need to be an absolute path. Note also that any changes you make to the label now will not change the icon because of the way Dockerman caches icons. I believe there are one or more earlier posts in this thread that describe how to manually remove the cached icon. 1 Quote
nearcatch Posted September 17 Posted September 17 6 hours ago, primeval_god said: The icon label is typically a web address, i am not sure if unRAID supports specifying local icons. If it does the path would certainly need to be an absolute path. Local icons definitely work with absolute paths, that's how all my icons are set for unRAID in my compose file. Quote
jerrt Posted September 24 Posted September 24 On 6/24/2022 at 3:57 AM, arifer said: Adding the following snippet under the "up" and "down" lines in "/usr/local/emhttp/plugins/compose.manager/scripts/compose.sh" successfully settled the problem raised by @Agent531C for the case of updating the web UI label. I can get the same result by first spinning down a stack, editing it, and then spinning it back up; as well as editing a stack and then recreating it by clicking on the "compose up" button on the web GUI. docker compose -f "$2" -p "$3" ps -a | awk '{if (NR!=1) {printf("%s.\"%s\"", sep, $1); sep=", "}}' | xargs -0 -I {} jq 'del({})' $DOCKER_JSON > $DOCKER_JSON docker compose -f "$2" -p "$3" up -d 2>&1 The following snippet is a cheap and dirty way of forcing unRAID to delete cached icons and retrieve them from the `net.unraid.docker.icon` label. I placed this udner the "up" "down" lines in the same file above. docker compose -f "$2" -p "$3" ps -a | awk '{if (NR!=1) {print $1}}' | xargs -I {} find $DOCKER_IMAGES $UNRAID_IMAGES -name {}.png -delete The environments used in the snippets are declared at the top of the file: DOCKER_MANAGER=/usr/local/emhttp/state/plugins/dynamix.docker.manager DOCKER_JSON=$DOCKER_MANAGER/docker.json DOCKER_IMAGES=$DOCKER_MANAGER/images UNRAID_IMAGES=/var/lib/docker/unraid/images This ability is exactly something Id like to impliment. Is this still valid for use in 2024? I am a bit green when it comes to editing the file as described. I get errors just dropping those sections into the file. Is there a best practices for this file? Anyway I could see a copy of the changes added to the compose.sh file? Many thanks in advance! Quote
Darkestnoir Posted October 8 Posted October 8 Today i wanted to add a docker container to my server, but my whole docker tab is again not working/responsive (with the Unraid logo wobbling over the screen). It ran for two month without issues, but now its f* again. Not sure where to start to fix this, probably it was caused by the last plugin update of the compose manager. I still hope the update thing also get fixed someday. Quote
bmartino1 Posted October 8 Posted October 8 Having issues using docker compose on unraid v7 beta 3 Not sure is there was a change done to the docker system... The progelm is affecting grafana only weridly enouth... Quote
primeval_god Posted October 10 Author Posted October 10 On 10/8/2024 at 5:44 AM, Darkestnoir said: Today i wanted to add a docker container to my server, but my whole docker tab is again not working/responsive (with the Unraid logo wobbling over the screen). It ran for two month without issues, but now its f* again. Not sure where to start to fix this, probably it was caused by the last plugin update of the compose manager. I still hope the update thing also get fixed someday. I am not aware of any changes that would cause the issue, nor have I seen any other reports of it. To debug I would suggest opening the developer options in your browser and watching the console for errors when reloading the docker page. Additionally in the latest version of this plugin there is an option (in the settings page) to break the compose plugin out of the docker page into it's own top level tab. You could try enabling that option and see if it's the compose tab of the docker tab that ends up being non responsive. 1 Quote
primeval_god Posted October 10 Author Posted October 10 @bmartino1 I cant really tell from your post what the issue with your grafana stack actually is. Is it something to do with the webui link or a continually restarting container? This plugin is not currently tested against unraid v7 (by me at least) so I am not yet familiar with the docker system changes for the beta3 version. If the issue is with the container rather than the webui integration could you tell me what version of the docker engine unraid v7 has? Quote
Darkestnoir Posted October 10 Posted October 10 28 minutes ago, primeval_god said: Additionally in the latest version of this plugin there is an option (in the settings page) to break the compose plugin out of the docker page into it's own top level tab. You could try enabling that option and see if it's the compose tab of the docker tab that ends up being non responsive. Ty, with this i just did a compose down and up and now everything is fine again. Quote
primeval_god Posted October 10 Author Posted October 10 1 hour ago, Darkestnoir said: Ty, with this i just did a compose down and up and now everything is fine again. Does the problem recur when switching back to compose in the docker tab? Quote
bmartino1 Posted October 10 Posted October 10 (edited) 4 hours ago, primeval_god said: @bmartino1 I cant really tell from your post what the issue with your grafana stack actually is. Is it something to do with the webui link or a continually restarting container? This plugin is not currently tested against unraid v7 (by me at least) so I am not yet familiar with the docker system changes for the beta3 version. If the issue is with the container rather than the webui integration could you tell me what version of the docker engine unraid v7 has? Was a weird issue I encountered with how dockers get information and wirte to docekrs configs. mainly affecting grafana docker only that i found. For me a issue within netprobe. as it only affected the grafana regardless if it was a compose file or not. (I even used the non compose form the ap store as well....) it was more a issue within the grafan image and a change in how its environment and variable code where grafan wasn't getting a ipv4 address nor a ipv6 address while having a hostname set(seen within the bug report). Then calling this for web UI access when the webserver failed. a glitch that only affect Grafana where when the unriad webui calls [ip] [port] I got its hostname continually with no connection as the ip wasn't resolvable and grafan webserver not running. I had to do quite a bit to fix grafan from deleting it image and reform compose, trying it standalone, same thing. I now have a working netprobe once more after updating the docker compose for grafana. Weirdness on unraid v7 beta 3. Reached on with a bug report, here and on the support for the appstore graffana image. Just bring it up. Edited October 10 by bmartino1 Quote
Darkestnoir Posted October 10 Posted October 10 (edited) 19 hours ago, primeval_god said: Does the problem recur when switching back to compose in the docker tab? No, because i did a compose down and up, but before i couldn't do this because the UI was unresponsive in the docker tab (yeah i know i can do it via the console, but its annoying 😅). Not sure why my UI was bugged this time, maybe it has something to do with auto updates from watchtower. But the update issue via the UI is still a thing, i am surprised that there is no fix for that. Edited October 11 by Darkestnoir Quote
pleasehelpmeguys Posted October 17 Posted October 17 How do i use the terminal in compose manager? Is there even one? I’m trying to run this command as per immichs instructions: docker compose down --remove-orphans. Thanks! Quote
primeval_god Posted October 18 Author Posted October 18 3 hours ago, pleasehelpmeguys said: How do i use the terminal in compose manager? Is there even one? I’m trying to run this command as per immichs instructions: docker compose down --remove-orphans. Thanks! You can run compose commands from the terminal as compose is installed system wide. You will however need to add the -f flags to specify the paths to your compose files. Quote
pleasehelpmeguys Posted October 18 Posted October 18 Thank you so much! I have no idea what i’m doing but i’ll try to read up on it haha. Quote
L0rdRaiden Posted October 27 Posted October 27 @primeval_god I'm trying to do this https://forums.docker.com/t/how-to-reference-several-env-file-with-absolute-paths/144653 Is there any limitation on how docker compose or docker is implemented in Unraid that doesn't allow my to do it? Basically I want to use several .env files in different places in the same docker-compose.yaml Thanks Quote
bmartino1 Posted October 27 Posted October 27 (edited) 2 hours ago, L0rdRaiden said: @primeval_god I'm trying to do this https://forums.docker.com/t/how-to-reference-several-env-file-with-absolute-paths/144653 Is there any limitation on how docker compose or docker is implemented in Unraid that doesn't allow my to do it? Basically I want to use several .env files in different places in the same docker-compose.yaml Thanks I'm only aware of the web ui and compose plugin allowing 1 env file you would need to combine all the env files in 1 .env file. I'm not aware but a include file could be used and called form the .env file... to point tot he other 7... Been a while... i think its source .env.env1-7..... added to the .env file to add additional envs... Otherwise your not using unraid web UI to do this... this could be done within the terminal... To add an include file to your .env in Docker Compose, you can follow this approach: Create an Include File: Add a new .env.include file (or any other name you prefer) where you’ll list other environment files to include. Use a Script to Source Files: Since Docker Compose doesn’t natively support .env file inclusion, you’ll need a workaround. You can use a shell script to source multiple .env files and export them for Docker Compose. Here’s a quick example: # include_envs.sh set -a # Automatically export all variables source .env.main # Main .env file source .env.additional # Additional .env file set +a docker-compose up Run Docker Compose Using the Script: Instead of docker-compose up, you’d run: ./include_envs.sh Edited October 27 by bmartino1 1 Quote
primeval_god Posted October 28 Author Posted October 28 18 hours ago, L0rdRaiden said: @primeval_god I'm trying to do this https://forums.docker.com/t/how-to-reference-several-env-file-with-absolute-paths/144653 Is there any limitation on how docker compose or docker is implemented in Unraid that doesn't allow my to do it? Basically I want to use several .env files in different places in the same docker-compose.yaml Thanks As far as I am aware there are no limitations that would prevent you from doing this. There is no support for editing the extra env files in the compose manager ui however. Quote
L0rdRaiden Posted October 28 Posted October 28 (edited) 19 minutes ago, primeval_god said: As far as I am aware there are no limitations that would prevent you from doing this. There is no support for editing the extra env files in the compose manager ui however. Ok, but I guess I would need to setup a script to run this on every array start with absolute paths (not relative like below) for all the docker-compose files that I want them to use 2 ENV files. And them in the same script do the compose up for all the docker compose files. Right? docker compose --env-file .env --env-file ../ininventory.env up -d Edited October 28 by L0rdRaiden Quote
primeval_god Posted October 28 Author Posted October 28 8 minutes ago, L0rdRaiden said: Ok, but I guess I would need to setup a script to run this on every array start with absolute paths (not relative like below) for all the docker-compose files that I want them to use 2 ENV files. And them in the same script do the compose up for all the docker compose files. Right? docker compose --env-file .env --env-file ../ininventory.env up -d Apparently i didnt read the info closely enough. It looked to me like they were showing referencing multiple env files by absolute path from within a compose file. Quote
L0rdRaiden Posted October 28 Posted October 28 (edited) 1 hour ago, primeval_god said: Apparently i didnt read the info closely enough. It looked to me like they were showing referencing multiple env files by absolute path from within a compose file. I finally found the solution but it would be perfect if it would be integrated in compose manager The change is "simple" it simply requires to add additional parameters to the up/down compose command docker compose -f /mnt/services/docker/docker-compose/Monitoring/docker-compose.yml --env-file /mnt/services/docker/docker-compose/Monitoring/.env --env-file /mnt/services/docker/docker-compose/.env up -d docker compose -f /mnt/services/docker/docker-compose/Monitoring/docker-compose.yml --env-file /mnt/services/docker/docker-compose/Monitoring/.env --env-file /mnt/services/docker/docker-compose/.env down Can you add support to this? like allowing several env files in the stack? Edited October 28 by L0rdRaiden 1 Quote
primeval_god Posted October 28 Author Posted October 28 2 hours ago, L0rdRaiden said: Can you add support to this? like allowing several env files in the stack? I will consider it, however such a feature runs counter to the general direction of the plugin. My goal for the plugin is to have a minimal set of features to support simple single file compose stacks. 1 Quote
L0rdRaiden Posted October 28 Posted October 28 33 minutes ago, primeval_god said: I will consider it, however such a feature runs counter to the general direction of the plugin. My goal for the plugin is to have a minimal set of features to support simple single file compose stacks. Well is your fault to make the plugin with an easy learning curve, now we want more as we learn. Hehehe just kidding thanks for the effort I appreciate that you will consider it Quote
karpiq Posted November 4 Posted November 4 How to reload .env file after changing values? Clicking Down & UP or Update buttons still uses old values. Quote
primeval_god Posted November 4 Author Posted November 4 4 hours ago, karpiq said: How to reload .env file after changing values? Clicking Down & UP or Update buttons still uses old values. You should just be able to click the up button. Bring the stack completely down and then back up shouldn't be necessary, but it should definitely cause your stack to pickup any changed values. Quote
Recommended Posts
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.