eafx

Hi there, I'm the dev for this repo. I've currently moved houses and will be moving again later this year, unfortunately my Unraid server is in storage, so haven't tested any of the new builds. I've merged your pull request, thanks for that @knaack Docker image should've been updated as well now, could you please pull and test when you get a chance?

That's great! and you found a bug as well nice! You can open a pull request if you want and I'll get that merged.

Can you post some screenshots of your config? Screenshots that show network type and extra parameters for vpn container, rebuild-dndc and any one container that you want it to use the vpn container network. Edit: Also take a look at this guide: https://www.reddit.com/r/unRAID/wiki/guides/vpndockernetwork

Think I know what your issue is, the "network type" on rebuild-dndc container should be bridge mode/it shouldn't be using the VPN container network. The reason it's stopping itself is because it's using the VPN container network (or at least at some point it was using the VPN network) and has marked itself as a container in-scope for rebuild. 1. Make sure rebuild-dnc isn't using the VPN container network. 2. Stop the rebuild container and delete all the *.tmp files in config\rebuild-dndc folder, better to clear any any previous misconfiguration and then restart it. 3. Some other useful tips Make sure the VPN container is the first container on your docker startup list Move the Rebuild-DNDC container to the end of your container startup list. Edit: Also, FYI the issue with bubuntux/nordvpn might've been resolved now. Problem was that container didn't have iputils-ping package installed and the rebuild container uses the ping command to check for connectivity on the VPN container. https://github.com/elmerfdz/rebuild-dndc/issues/52 and seems like that has been implemented now: https://github.com/bubuntux/nordvpn/issues/163

Once you deploy the vpn container, you need to make sure it's working/connected, only then start the rebuild-dndc container. "- CONNECTIVITY: BROKEN" message suggests that there might be an issue with your vpn container connection i.e. rebuild-dndc is unable to ping (via your vpn container) any of the set dns servers (CF or Google) to check for an active connection, hence it's restarting your vpn docker hoping that would fix the connectivity issue.

Sweet! thanks! 🙂

missing on the context menu.

On the docker page for that container.

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

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.

Will it also work, if I set it to auto update the vpn container using the CA Auto Update plugin?

Is there a reason why it rebuilds only when the Docker page is opened?

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.

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.

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

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?

Seems like it's hitting some character limit, it won't let me save past certain number of lines/characters.

Happens only when using my own custom variables, no issues saving random text or css otherwise.

@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?

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).

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.

See my comments on this thread:

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

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.

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.