build: healtcheck defined in dockerfile does not apply to all use-cases

[kopernic-pl]

healtcheck defined in dockerfile does not apply to all use-cases (comands) for image, causing healtcheck failed when using compose when no healthcheck exists

SUMMARY

Container healtcheck from dockerfile checks connectivity to locally running 8088 - which is running only in 'superset' container, not workers or beats or init one

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

run compose /dev compose - there should be no failed healtcheck containers running

ADDITIONAL INFORMATION

• Has associated issue: unhealthy "app" and "worker" docker containers #12895
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[kopernic-pl]

Possibly somewhat related to #13129

[craig-rueda]

Does it make sense to yank this out of the docker file instead? Then you can just re add it into the superset container only in the compose file. Or just leave it out all together. I'm not convinced we need it for compose.

[kopernic-pl]

There is one image that does multiple things. It has healthcheck inside but only for one aspect of its operations. I agree that moving HC out and defining it externally is a good idea.