-
Notifications
You must be signed in to change notification settings - Fork 2k
0.4.0 Milestone Project Page
- 07/21/2015 - Code Freeze
- 08/11/2015 - Release
Along with Docker 1.8, we will be deprecating the Boot2Docker installers in favor of a installer that recommends Machine.
In 0.3.0 we added support for migrating VMs from the Boot2Docker installer to Machine and deprecated the Boot2Docker CLI. This will finalize the migration by moving to an official Docker supported minimal Machine operating system for local environments.
- P1 Installers with Machine, etc
- P1 Finalize migration and usage docs
- P2 B2D OS replacement
The creation process varies greatly from provider to provider. Issues like network partitions, provider API hiccups, etc can cause issues. Currently, Machine does not handle those very well. Errors are not always reported well and the user must remove whatever has been created and start over. This affects users using Machine directly as well as indirectly (i.e. Kitematic, Rancher, Machinery). We should improve the provision process to handle various types of failure and better report them when they occur. This could include the ability to re-provision an existing host in the even upon failure.
- P1 Debug Logging to file by default for retrieval
- P2 Command to retrieve debug and error logs for any command
- P3 Provisioning retries
In 0.3.0 we added several improvements for the VirtualBox provider however, the user experience is still a bit lacking for the other "local" providers. Machine 0.3.0 also added support for VMware shared directories however not all features for local drivers match. For example, VirtualBox on Linux does not map shared directories. Hyper-V does not have shared directories at all. We should work to get the local drivers as stable and feature complete as possible.
- P1 VirtualBox provisioning and usage stability
- P2 VirtualBox, Fusion, Hyper-V improved integration testing
- P3 Fusion stability from VMware
- P3 Hyper-V stability from MSFT