InternalCommandPortListeningCheck always fails for containers built without `/bin/sh`
#3 317 ouverte le 11 oct. 2020
Métriques du dépôt
- Stars
- (7 535 stars)
- Métriques de merge PR
- (Merge moyen 2j 17h) (2 PRs mergées en 30 j)
Description
Relates to #2984
I'm surprised we've not come across this earlier, but the default TCP port listening detector InternalCommandPortListeningCheck does not work for containers that do not have /bin/sh included.
This predominantly affects images built upon scratch.
The workaround/solution is to use a more application specific WaitStrategy - e.g. an HTTP wait strategy.
However the log messages don't make this easy to realise.
Given that we do both the internal and external port checks for a good reason, I don't think we can just rely on the external port check. Still perhaps we can raise a very specific error message if /bin/sh is not available inside the container.