-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use a static domain name to avoid cert errors when the VM IP changes #136
Comments
I've been meaning to add this to the FAQ, thanks for the reminder: https://github.com/codekitchen/dinghy/blob/master/FAQ.md#the-docker-client-reports-errors-like-x509-certificate-is-valid-for-192168xy-not-192168xz I haven't seen it happen as often as whenever you switch networks though. It seems to happen to most people once every few months or so. So there may be something more going on in your situation. It'd be nice if docker-machine detected the situation and handled it automatically, I haven't checked open issues to see if they're planning to do that. |
@codekitchen ah, that makes sense. I thought it might be a docker-machine issue. I think it might be happening because I'm switching between a work and home network where there's a different DHCP reservation set up for my host machine, but I'm not sure. Do you know if it's possible to force docker-machine to generate a certificate for a local domain name instead? Perhaps dinghy could solve this issue by setting DOCKER_HOST to something like |
Yeah interesting idea, it seems like that'd work. |
yeah, this is really problematic. Recreating is no option for me, since pulling or building my docker container takes about 30 minutes (cotains over 2GB of NLP libraries). What's the best workarround for now. Can I just not set @robbles what do you mean with “passing |
As stated in the FAQ answer I linked to, the fix is to run |
@MrLoh do you have an older version of docker, or an out of date version of the VM created by docker-machine? |
@MrLoh in other words, I think it's likely that either solution will work for you if you recreate your VM this one time, in order to bring it up to date. |
thanks the |
something.docker
something.docker
When I switch networks and end up with a different IP address, I get an error like this:
Restarting dinghy doesn't help, but recreating the VM with
dinghy destroy && dinghy create --provider virtualbox
seems to fix it.Is it possible to make this more resilient? Or is there just a configuration setting I'm missing? I think that recreating the dinghy instance every time I switch desks is not really reasonable, and neither is passing
--tlsverify=false
with every docker command.The text was updated successfully, but these errors were encountered: