If you build the Dockerfile manually on your machine, the checksum will be exactly the same as the one seen on Docker Hub. I then simply just added the IP of the NxFilter installation to be the first DNS Server in the list of DNS Servers handed out by the DHCP Server on router and added the IP of router and it's DNS Resolver as the upstream DNS server of NxFilter. You know exactly what is going into the image in an easy to reproduce way. To try I just installed NxFilter as a docker container on server with it's own LAN ip.

Docker hub will always use the latest version of the Dockerfile on Github linked below. Every time a new version of NxFilter is released on or the Dockerfile is updated on Github, an automated build is triggered to go download the latest version of NxFilter or NxFadmin and build the image. moby/moby () Or you can try to stop 'Watchtower' and then reinstall Portainer via the OMV GUI and do a re-deploy of the rest of the containers to pull the latest images to see if it solves itself.This means you can see exactly how the image is built. docker daemon unable to access registry - Client.Timeout exceeded while awaiting headers

We also provide an image with NxFadmin preinstalled should that be your preference.īoth images are automated builds on Docker Hub. It provides a very quick and easy way to deploy NxFilter to an existing Docker infrastructure.

I am very excited to share this with everyone and feel like the NxFilter Docker image is almost ready for prime time. Some of you may already be using this, but figured I would share with those who are not.

Nxfilter docker