vagrant-lxc-ng/CHANGELOG.md

0.8.0 (unreleased)

FEATURES:

• Support for naming containers from Vagrantfiles #132

IMPROVEMENTS:

• Use a safer random name for containers #152

BUG FIXES:

• Properly detect if lxc is installed on hosts that do not have lxc-version on their paths #186

0.7.0 (Nov 8, 2013)

IMPROVEMENTS:

• Support for vagrant up in parallel #152
• Warn users about unsupported private / public networking configs #154
• Respect Vagrantfile options to disable forwarded port #149

BUG FIXES:

• Nicely handle blank strings provided to :host_ip when specifying forwarded ports #170
• Fix "Permission denied" when starting/destroying containers after lxc security update in Ubuntu #180
• Fix vagrant package #172

0.6.4 (Oct 27, 2013)

FEATURES:

• New script for building OpenMandriva base boxes #167

IMPROVEMENTS:

• Make lxc-template compatible with Ubuntu 13.10 #150

BUG FIXES:

• Fix force halt for hosts that do not have lxc-shutdown around (like Ubuntu 13.10) #150

0.6.3 (Oct 12, 2013)

IMPROVEMENTS:

• Respect Vagrantfile option to disable synced folders #147

BUG FIXES:

• Fix error raised when fetching container's IP with the sudo wrapper disabled #157

0.6.2 (Oct 03, 2013)

IMPROVEMENTS:

• Cache the result of lxc-attach --namespaces parameter support checking to avoid excessive logging.

BUG FIXES:

• Fix detection of lxc-attach --namespaces parameter support checking.

0.6.1 (Oct 03, 2013)

IMPROVEMENTS:

• Fall back to dnsmasq leases file if not able to fetch IP with lxc-attach #118
• Make sure lxc templates are executable prior to lxc-create #128
• New base boxes with support for lxc 1.0+

BUG FIXES:

• Fix various issues related to detecting whether the container is running and is "SSHable" #142
• Nicely handle missing templates path #139

0.6.0 (Sep 12, 2013)

IMPROVEMENTS:

• Compatibility with Vagrant 1.3+ #136
• Set plugin name to vagrant-lxc so that it is easier to check if the plugin is installed with the newly added Vagrant.has_plugin?

BUG FIXES:

• Fix box package ownership on vagrant package #140
• Fix error while compressing container's rootfs under Debian hosts #131 / #133

0.5.0 (Aug 1, 2013)

BACKWARDS INCOMPATIBILITIES:

• To align with Vagrant's core behaviour, forwarded ports are no longer attached to 127.0.0.1 and redir's --laddr parameter is skipped in case the :host_ip config is not provided, that means redir will listen on connections coming from any of the host's IPs.

FEATURES:

• Add support for salt-minion and add latest dev release for ubuntu codenamed saucy #116
• Add support for using a sudo wrapper script #90
• redir will log to /var/log/syslog if REDIR_LOG env var is provided

IMPROVEMENTS:

• Error out if dependencies are not installed #11 / #112
• Support for specifying host interface/ip for binding redir #76
• Add Vagrantfile VM name to the container name #115
• Properly handle forwarded port collisions #5
• Container's customizations are now written to the config file (usually kept under /var/lib/lxc/CONTAINER/config) instead of passed in as a -s parameter to lxc-start

0.4.0 (Jul 18, 2013)

FEATURES:

• New box format #89

BUG FIXES:

• Add translation for stopped status #97
• Enable retries when fetching container state #74
• Fix error when setting Debian boxes hostname from Vagrantfile #91
• BTRFS-friendly base boxes #81
• Extended templates path lookup #77 (tks to @aries1980)
• Fix default group for packaged boxes tarballs on the rake task #82 (tks to @cduez)

0.3.4 (May 08, 2013)

FEATURES:

• Support for building Debian boxes (tks to @Val)
• Support for installing babushka on base boxes (tks to @Val)

IMPROVEMENTS:

• Replace lxc-wait usage with a "retry mechanism" #22
• Remove /tmp files after the machine has been successfully shut down #68
• Clean up base boxes files after they've been configured, resulting in smaller packages
• Bump development dependency to Vagrant 1.2+ series

BUG FIXES:

• Issue a lxc-stop in case the container cannot shutdown gracefully #72

0.3.3 (April 23, 2013)

BUG FIXES:

• Properly kill redir child processes #59
• Use uname -m on base Ubuntu lxc-template #53

IMPROVEMENTS:

• Initial acceptance test suite
• New rake tasks for building Ubuntu precise and raring base amd64 boxes

0.3.2 (April 18, 2013)

• Do not display port forwarding message in case no forwarded ports were set

0.3.1 (April 18, 2013)

• Improved output to match lxc "verbiage"

0.3.0 (April 10, 2013)

BACKWARDS INCOMPATIBILITIES:

• Boxes lxc-template should support a --tarball parameter
• start_opts config was renamed to customize, please check the README for the expected parameters
• V1 boxes are no longer supported
• target_rootfs_path is no longer supported, just symlink /var/lib/lxc to the desired folder in case you want to point it to another partition
• Removed support for configuring private networks. It will come back at some point in the future but if you need it you should be able to set using customize 'network.ipv4', '1.2.3.4/24'

IMPROVEMENTS:

• lxc templates are removed from lxc template dir after container is created
• Treat NFS shared folders as a normal shared folder instead of ignoring it so we can share the same Vagrantfile with VBox environments
• Support for lxc 0.7.5 (tested on Ubuntu 12.04) #49
• Remove /tmp files when packaging quantal64 base box #48
• Avoid picking the best mirror on quantal64 base box #38

BUG FIXES:

• Redirect redir's stderr output to /dev/null #51
• Switch from ifconfig to ip to grab container's IP to avoid localization issues #50

0.2.0 (March 30, 2013)

• Experimental box packaging (only tested with Ubuntu 64 base box)

0.1.1 (March 29, 2013)

• Removed support for development under Vagrant < 1.1
• Removed rsync from base quantal64 box to speed up containers creation #40
• Containers are now named after project's root dir #14
• Skip Vagrant's built in SSH redirect
• Allow setting rootfs from Vagrantfile #30

0.1.0 (March 27, 2013)

• Support for chef added to base quantal64 box
• Puppet upgraded to 3.1.1 on base quantal64 box
• Port forwarding support added #6

Previous

The changelog began with version 0.1.0 so any changes prior to that can be seen by checking the tagged releases and reading git commit messages.