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

[Drew Gibson]

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
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20150515/7da587f5/attachment.html>