-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes to the the icon and webui labels not upheld #9
Comments
The ability to specify images using labels is a feature of unRAID 6.10. If this is not working correctly due to their caching mechanism i would rather raise the issue to them first than try to patch around it myself. Especially since handling of icon labels is not yet built into this plugin. |
If you intend to raise it up as an issue upstream, there will necessarily be a If we look back at the git logs for limetech/webgui, the last commit relating to |
This is in reference to the issue brought up in the unRAID forum
post
by Agent531C. Changes to
net.unraid.docker.icon
andnet.unraid.docker.webui
are not reflected after running either
compose up
orcompose down
. Thereason for this is that unRAID stores all the information in the cache and does
not clear it unless 1 of 2 situations occur:
/usr/local/emhttp/state/plugins/dynamix.docker.manager/docker.json
andits related files are deleted.
(usually on a reboot).
While it would be great to implement the changes to the unRAID OS, the fact of
the matter is that docker compose is not officially supported yet. It would be
more appropriate for now to have these changes implemented as part of how
compose projects are spun up and down in this plugin. It is possible for
example, delete a project's services from the
docker.json
file to ensure thatwebui labels are properly updated whenever a project is spun up again. For
icons, deleting the relevant image files in both
/usr/local/emhttp/state/plugins/dynamix.docker.manager/images
and/var/lib/docker/unraid/images
should be sufficient to force unRAID to retrievethe correct image.
The text was updated successfully, but these errors were encountered: