Starting Quarkus 2.6, Quarkus can compress the produced native executable using UPX. To avoid having UPX installed locally when the user uses an in-container-builder, Quarkus tries to use the UPX executable offered by the builder image. The community builder images have been updated to provide the `upx` command.
 
This issue is about whether the same should happen for the productized builder image. 
 
If the image does not provide upx, the user will be informed that it does not provide it and should install upx on the machine.  This, of course, only happens if compression is enabled