Closed mibere closed 6 years ago
Hi!
Both are equivalent, but the former omits quite a few important details described in the later. So, I'd recommend the later.
We should really merge both to avoid confusion.
Yeah, I'm confused ;-)
The one works with a volume
docker run -d --volumes-from ...
in the other the keys are copied manually
docker cp ~/keys/. ...
Two completely different methods.
Ok, my server seems to be back with Unbound 1.7.1.
The steps in https://github.com/jedisct1/dnscrypt-proxy/wiki/Manually-updating-your-DNSCrypt-server are ok, with one exception:
docker exec dnscrypt-server-new rm -rf /opt/dnscrypt-wrapper/etc/keys/short-term
does not work because the server is not started at this point. Error message:
Error response from daemon: Container e24b....4b2fa is not running
So I had to use
docker start dnscrypt-server-new docker exec dnscrypt-server-new rm -rf /opt/dnscrypt-wrapper/etc/keys/short-term
Good catch.
The missing command has been added to the wiki.
Hi Frank,
what's the recommended way to update an already installed and running docker image?
I ask because you have two different how to's:
https://github.com/DNSCrypt/dnscrypt-server-docker/wiki/Update-Docker-image
https://github.com/jedisct1/dnscrypt-proxy/wiki/Manually-updating-your-DNSCrypt-server