This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 183
How to upgrade? #46
Comments
With the VM running :
seems to work and maintain persisted things. |
@dduportal Can you elaborate? I have a docker-proxy vagrantfile in my project that does some additional port forwarding. Example: Vagrant.configure("2") do |config|
config.vm.box = "mitchellh/boot2docker"
config.vm.provider "virtualbox" do |v|
v.check_guest_additions = false
v.functional_vboxsf = false
v.memory = 2048
v.cpus = 2
end
config.vm.network "forwarded_port", guest: 80, host: 8080
config.vm.network "forwarded_port", guest: 2003, host: 2003
config.vm.network "forwarded_port", guest: 8125, host: 8125
# b2d doesn't support NFS
config.nfs.functional = false
end How would I upgrade this box to b2d v0.9.1? Currently my OSX docker client is failing with |
I tried to update using your instructions above:
|
Confirmed, I'm still getting b2d v0.8.0:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With Docker's script, it's
boot2docker stop
—boot2docker download
—boot2docker start
. It says that the VM's hard drive isn't affected. What's the way to do this with Vagrant? Vagrant requires destroying the image in order to change the underlying image, no?Ref: http://docs.docker.io/installation/mac/#upgrading-to-a-newer-release-of-boot2docker
The text was updated successfully, but these errors were encountered: