[lxc-users] How to run scripts when container is destroyed?

[Sungbae Yoo]

Hi,

Thank you for your opinion.

it will be overhead to install another management tool just for execute some
jobs when container is destroyed.

In LXC, I think that template is very nice because user can be create easily
by using lxc-create.
Similarly, user should be able to destroy easily just using lxc-destroy,
don't care about restoring environment that might be changed by container.
Without any tool.

Best regards,
Sungbae Yoo


------------------------------------------------

From: lxc-users [mailto:lxc-users-bounces at lists.linuxcontainers.org] On
Behalf Of Drew Gibson
Sent: Saturday, May 16, 2015 1:31 AM
To: LXC users mailing-list
Subject: Re: [lxc-users] How to run scripts when container is destroyed?

Hi,

while not wishing to argue against the usefulness of lxc.hook.destroy,
it seems to me that functions 1 & 2 would be better performed at a system
level rather than within LXC.

A configuration management tool (such as Puppet or Chef) is aware of
requirements beyond the scope of an individual container before performing
an action that may impact other parts of the system such as removing a
package or stopping a service.

OTOH, I can seethe use for an email notification when a container is
destroyed.

just my 2 cents/tuppence worth ...

regards,

Drew

------------------------------------------------

On 14/05/15, Sungbae Yoo <sungbae.yoo at samsung.com> wrote:
Hi,

I uploaded commit to add lxc.hook.destroy to config.
https://github.com/lxc/lxc/pull/522

It will be take a long time to release a template I making.
But we need lxc.hook.destroy for following.
1. uninstalling some package such as shortcut application to start the
container.
2. disabling some systemd services needed for container.
3. the way to notify container is destroyed.

Best regards,
Sungbae Yoo.

_______________________________________________
lxc-users mailing list
lxc-users at lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users