-
Bug
-
Resolution: Unresolved
-
Critical
-
2.2.3.CR5
-
False
-
False
-
+
-
Setting the `quarkus.openshift.arguments` property, for example `quarkus.openshift.arguments=ARG1,ARG2`fails when using the Quarkus OpenShift extension for Native builds. The resulting YAML file is openshift using arguments.yml and the deployment fails with:
Error: container create failed: time="2021-10-14T08:03:53Z" level=error msg="container_linux.go:367: starting container process caused: exec: \"ARG1\": executable file not found in $PATH"
It seems that the problem is that the image `ubi-quarkus-native-binary-s2i:1.0` is using the `argument` parameter to locate the binary instead of the `command` parameter.
Using the OpenShift extension with Docker build happens the same.
For JVM, it works fine.