Containers known to cause issues

The issue

The Supervisor needs to be the only manager of the containers that it manages, unfortunately, some other containers also take on this role. Worst case, those will auto-update the existing containers to development builds without consideration of the channel you have chosen. Because of this, a few containers known to cause issues, have been added to a denylist that will flag your installation as unsupported.

As stated in ADR-0014, running additional software on the host is not supported, and more containers or other software can be added to the denylist without any notice.

The solution

You will find a list of offending containers in your Supervisor log.

If you remove all offending containers from your host and then reload the Supervisor, it will no longer be marked as unsupported for this reason.