This question (starting container process caused: error loading seccomp filter into kernel: loading seccomp filter: errno 524: unknown) is on-topic, right? The host OS is Ubuntu 20.04, and the container OS is Ubuntu 14.04.
In my opinion, containers are the exact solution to running ancient stuff without polluting your base system.
Yeah. On-topic.
People can focus on the minutia, make arguments about kicking it off to another site or demanding they update the container (how? it's not booting!) but we have to remember we're here to help people.
The host system seems to be the problem here. Let's help them rather than mummify them in red tape.
If it does transpire to be a problem in the container, that serves as a good answer for other people bumping into the same problems with their older containers. Because people do deliberately run on old-version-Ubuntu containers because that's the only way people can run their software. I've had to do that for local services that have been uneconomical to upgrade.
At first, this seems like an ideal solution.
But are we allowed to ask questions about the containerized OS if it is past EoSS? Or just about the container?
If so, we should stop playing games and go back to allowing questions up to EOL (with or without ESM).
If Canonical can support an LTS version for ten years, I am sure Ask Ubuntu also has enough talent to do likewise.
In this, I'd say we should treat them like VMs. We can help with getting the containers to start, and problems with interfacing the containers with host (like networking), but problems that are purely inside the containers would be out of scope if the OS inside the container is out-of-scope.
