boot2docker 1.7.0 cert fix

profile

wait4eth1() {
        CNT=0
        until ip a show eth1 | grep -q UP
        do
                [ $((CNT++)) -gt 60 ] && break || sleep 1
        done
        sleep 1
}
wait4eth1

Instead of this, I opted for boot2docker delete, boot2docker init, boot2docker up.

Excellent article!! Happened the same to me about the WARNING. For me boot2docker delete is a pain option.

Straight to the point! Guys, if anyone is having issues with their containers not connecting to the internet(apt-get update fails), make sure you do a clean reboot of your computer.

Yes!

Thanks. works after forced power off at first time

Thanks! Awesome quick fix.

thanks

Top! Thanks!

In my case

$ boot2docker ssh
$ sudo /etc/init.d/docker stop
$ sudo /etc/init.d/docker start
Need TLS certs for boot2docker,127.0.0.1,10.0.2.15,192.168.59.103
-------------------
Generate server cert
/usr/local/bin/generate_cert --host=boot2docker,127.0.0.1,10.0.2.15,192.168.59.103 --ca=/var/lib/boot2docker/tls/ca.pem --ca-key=/var/lib/boot2docker/tls/cakey.pem --cert=/var/lib/boot2docker/tls/server.pem --key=/var/lib/boot2docker/tls/serverkey.pem
2015/06/26 02:49:48 Generating a server cert

it worked.

+1 for comment above.

Original script mentioned in this gist causes my boot2docker machine to hang on start, and the only solution which remains after it is to delete it and re-init back. Instead of this I tried stopping and starting docker daemon inside boot2docker machine and it worked for me.

The original script works but the boot2docker will hang on start, instead of deleting the image I force poweroff and restart and it boots right into it immediately, hooray!

Same here: it hangs on start after applying this patch, so I forced a poweroff of the VM and then restarted successfully.
If I just run boot2docker delete, boot2docker init, boot2docker up it works but then the second time I stop and start it I again see the certificate error, while after applying this solution it disappears permanently.

After applying the proposed fix and launching boot2docker the machine would go into an indefinite wait:

Waiting for VM and Docker daemon to start.................oooooo

I had to stop, delete and recreate the VM and then followed @y16ra's comment. Everything went back to working normally.

+1

👍

@adamkdean that worked for me:

boot2docker delete
boot2docker init
boot2docker up

Thank you

Thanks, works for me on Windows 7.

@y16ra
got it, thank you.

I was facing the problem as @jluna79.
Thank you for @y16ra's comment. It works for me on windows 8.1

The @y16ra's comment seems to be deleted. Can anyone paste here the solution, please? My boot2docker also hangs on start

Followed @y16ra suggestion and it worked.
(At least for now. Still don't know if I need to repeat the procedure in the future.)