Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by eafx

  1. missing on the context menu.
  2. On the docker page for that container.
  3. Not bothered about the update not showing on the context menu. It's just if you're using a private repo, it will always show there's an update available for that container on the dashboard (i.e. the container name is in blue text) even though it's already up to date. This behaviour was fixed in 6.8.1 but now it's back with 6.8.3
  4. Upgraded from 6.8.2 without any issues. Noticed one thing, the following change was introduced in 6.8.1, has this been removed in 6.8.3? I've got a private docker repo, which is now showing as there's an update available even if I try re-pulling the image. Think the above change in 6.8.1 fixed it for me but now it's back. Edit: when I say it's showing as update available, I mean container name is in blue but It doesn't give me an option to update the container on right-click.
  5. Will it also work, if I set it to auto update the vpn container using the CA Auto Update plugin?
  6. Is there a reason why it rebuilds only when the Docker page is opened?
  7. Official image builds the app package from source, I'm grabbing their GH releases. I'm using my own alpine image as the base image of this container, which is basically a fork of lsio's alpine-base, that has s6-overlay installed (used for setting PUID/GUID and running service scripts). TBH I don't see the point of merging this with the official image. I would suggest you open up an issue on their GH requesting to add support for PUID/GUID, let's see what they say.
  8. It's not a fork and a different approach to the official one, so don't think there's a chance it will be merged.
  9. I've created my own image for this, added support for: PUID/GUID TZ Supports app update on container restart (can disable this) Added support for optional run flags like verbose logging & env var file support. https://hub.docker.com/r/eafxx/statping
  10. Works as expected now thanks! If I want to include my theme with the plugin, does my theme need to use the plugin variables or can I have it set entirely within custom styling?
  11. Seems like it's hitting some character limit, it won't let me save past certain number of lines/characters.
  12. Happens only when using my own custom variables, no issues saving random text or css otherwise.
  13. @Skitals I'm trying to use my own custom variables for my theme in 'custom styling (advanced)' , so whenever I try to save my css with the :root { } block it won't save it, to get it to work I have to either get rid of root block or manually edit the theme's css file and then it will show up fine on the plugin but it won't allow me to edit & save it from the plugin. Any idea what's going on here?
  14. I like the docker management in Unraid. What I would like to see in 2020, is a responsive web design, better discord/webhook intergration and better VM management (Quick checkpoint creation & restore).
  15. This issue started with 6.8.0-rc1, which updated docker to v19.03.3. In this & newer docker releases, Docker won't accept multiple '--net' arguments/support connecting to multiple network endpoints. 'Network type: none' already adds the network argument (--net='none') to the docker run command, so when you add --network='container:vpn' or --net='container:vpn' to extra arguments, it doesn't override the 'Network type: none' already specified on the docker template, thus trying to connect to 2 network endpoints. A workaround to this issue, is mentioned on the linked thread above.
  16. See my comments on this thread:
  17. FYI: I've containerised this script and it's available on 'Community Applications', search for: Rebuild-DNDC and refer to the readme on https://github.com/elmerfdz/UnRAIDscripts before deploying the container
  18. For me, my containers started spinning up in the usual time it takes to do that, didn't notice any difference compared to previous version. Only the array status in the footer took awhile to update but I could access all my shares/drives. The array status on the main page was correct though.
  19. Another minor issue, the 'orphan image' image is broken. The image doesn't exist in this /webGui/images/disk.png location, it was missing in 6.8.0-RC3 as well.
  20. Updated fine from 6.8.0-RC3 but the array status in the footer is stuck at the following message But the array has already started, I can access all disks (read/write), docker containers are up & running. It's already over 20mins now and the status still hasn't changed. Main tab shows array has started as well. EDIT: The array status in the footer has changed to 'started' now, after almost an hour. titan-diagnostics-20191024-1021.zip
  21. Here ya go mate: https://github.com/elmerfdz/UnRAIDscripts Let me know if the instructions aren't clear or if you have any issues.
  22. Any containers relying on the VPN container will have to be removed & re-created when the container updates or when it's recreated, it's more of a docker issue than Unraid, as docker expands the value of --net=container:nordvpn to container ID even if you specify the container name, which is really annoying. So I've written a script that runs every 5mins using the 'user scripts' plugin, which checks if the VPN container ID has changed, if the containers are still using the current VPN container ID, adds containers using the VPN network to it's watch list and removes/recreates when required.
  23. Got back into the GUI by linking local addresses, disabled/enabled bonding and added eth0, eth1, eth2, eth3 back in, that seems to have done the trick. Done couple of reboots since, also updated back to 6.8.0-rc3 & done 2 reboots post that and everything is still working fine. Going to leave my logs up, hopefully you can find the root cause.