New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
latest version of SolusVM forces container to start if disabled?
linuxthefish
Member
in General
After setting an openvz container to disabled with vzctl or nodewatch, it seems the client can start the container again through solusvm.
Anyone else seen this?
Comments
Could be that the client simply re-installed the container and thus wiped the old openvz conf?
Its best if you use the nodewatch hook to also suspended the solusvm account instead of just stopping the container itself so they no longer have the ability to re-install for example
nodewatch uses vzctl to disable containers. So I imagine solusvm identified it as a stopped container. As @Zappie mentioned, use nodewatch solusvm suspending feature. It will suspend container rather than just stopping it.