Unfortunately, we have seen cases where Portainer possibly interferes. In normal setups, it should also not be needed to run Portainer directly, nor does the general goal of running Portainer fit Home Assistants architectural guidelines/goals (Supervisor and Portainer both have the goal of orchestration, which is conflicting).
In most cases, it will actually cause more problems for lesser experienced users that have no idea what they are getting themselves into. Yet, those lesser experienced users, are the main target audience for this installation method and the ones that need to be protected from getting themselves into impossible situations. More often resulting in support requests, issue reports, end-user frustrations, and an overall bad user experience.
If one really wants to work directly with Docker and has the experience, we, of course, offer the Home Assistant container installation method; which would be a much better fit for you in that case.
Anyways, we provide the means to override/disable these checks, if you really wish, using the CLI tools: ha jobs options --ignore-conditions healthy
Please note, this will render your system into an unsupported state (as running additional containers is not supported anyways, as is also documented).
Going to close the PR on this end, as an advanced option/alternative is offered.
…/Frenck