Skip to content

Container always starts after setup #51

Description

@mdkent

Found a small bug in setting up a new container: it's always being started and stopped despite having no work to do, eg: no chef support or container/initialize commands to run.

[2014-06-12T07:02:16+00:00] INFO: template[/var/lib/lxc/test/rootfs/root/.ssh/authorized_keys] mode changed to 600
[2014-06-12T07:02:16+00:00] INFO: ruby_block[lxc lock_default_users] called
[2014-06-12T07:02:17+00:00] INFO: ruby_block[lxc start[test]] called
[2014-06-12T07:02:23+00:00] INFO: ruby_block[lxc shutdown[test]] called
[2014-06-12T07:02:23+00:00] WARN: Cloning resource attributes for directory[/opt/hw-lxc-config] from prior resource (CHEF-3694)

Pull request follows.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions