Neat. But what about flmaxey's pi-hole docker tutorial that says this:
** If upgrading to the latest image, it is recommended that the previous container is stopped/deleted, delete the previous image, delete the macvlan driver in the networks tab and delete the file contents of /dockerparms/pihole . [/b]Then proceed with the installation of the new image as follows.**
Sounds a lot more involved than what you describe. Sounds like starting over every time.
The How-To was written to cover as many cases as possible. From PM's and threads, in a couple cases, problems were experienced in upgrading the image and container to the latest version, when the older volumes and bind points were retained. In one case, the macvlan interface refused to be reused. In these cases, if the older bind volumes and points and the macvlan interface are deleted, the new Pi-hole container works as intended. Since there's no way to determine how many are affected, it made sense to edit the How-To to take these issues into account.
When I upgrade, I've had no problem with reusing the macvlan interface and the older volumes and bind points merged seamlessly into the new version. (Which retains custom black and white lists and other settings.)
Thinking about it, perhaps an update is order, so that those without the fringe issues (the majority) can merge their settings into a new container.