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

[Sungbae Yoo]

Hi,

I just think a service that create a network bridge only for containers.
When container is destroyed, if this is the last one,
This service doesn't need to run.

But your opinion is right except for clear case as it mentioned above.
It will be dangerous to remove system service when container is destroyed.
Because the service can be used for the others, even though container don't know about.

Best regards,
Sungbae Yoo.


-----Original Message-----
From: lxc-users [mailto:lxc-users-bounces at lists.linuxcontainers.org] On Behalf Of Andrey Repin
Sent: Friday, May 15, 2015 10:58 PM
To: Sungbae Yoo; All
Subject: Re: [lxc-users] How to run scripts when container is destroyed?

Greetings, Sungbae Yoo!

>> This has me always wondering.

>> How do you know that only your container is using the service?

>> Last time I saw this idiocy is when iSCSI service was blindly killing 
>> all _netdev mounts when stopped. Guess, how many NON-iSCSI shares were killed?

> I mean the services that added newly for containers when container is 
> created. Not for the existed before.

I understand, that they were added when container was created.
How do you know, that they aren't used by anything else NOW?


--
With best regards,
Andrey Repin
Friday, May 15, 2015 16:56:30

Sorry for my terrible english...

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