Description
Abstract: many types of kiosk environments would benefit from being able to run an executable after the application started by cage exits.
As an example, cage is being used in my environment to start a frontend for arcade game emulators; the machine it's running on is physically located inside of an arcade game cabinet. Gracefully exiting the frontend is necessary in order to commit unsaved changes, and being able to power off the machine after exiting the frontend is necessary in order to keep people who aren't me from sticking their hands in places they shouldn't be in order to turn off the machine :)
As a workaround, I'm having cage start a bash shell which in turn runs a script that launches the frontend with '&& systemctl poweroff -i' specified. The cage user has sudo permissions to specifically run `systemctl poweroff -i', and everything shuts down as expected when leaving the frontend. While this works, starting a shell in order to run the application and shut the system down isn't really ideal.
If this type of functionality could be brought into cage directly, it would add a ton of flexibility. Obviously there are wider uses for this than just controlling power, but that seems like one which would have a lot of commonality across kiosk installations.