Inactive Container

When a container is deactivated, the resource boundaries are no longer enforced. A deactivated container enters into an inactive state and is deleted from the host's /etc/project file. While inactive, the container still exists in the software's database, pending future activation. Once the inactive container is reactivated, the container's resource boundaries are again enforced.

All data collected about the container's use of resources while it was active is preserved in the database. You can still request utilization reports for an inactive container for up to 30 days after the container was deactivated.