I managed to use "WILDFLY_SERVER_CONFIGURATION" successfully BUT I now get another issue...there is not any `standalone-full.xml` to use in `wildfly-centos7`. The error I can see in the logs is

java.lang.IllegalStateException: WFLYCTL0214: Could not get main file: standalone-full.xml. Specified files must be relative to the configuration dir: /opt/wildfly/standalone/configuration
	at org.jboss.as.controller@18.0.4.Final//org.jboss.as.controller.persistence.ConfigurationFile.determineMainFile(ConfigurationFile.java:373)
	at org.jboss.as.controller@18.0.4.Final//org.jboss.as.controller.persistence.ConfigurationFile.<init>(ConfigurationFile.java:207)
	at org.jboss.as.server@18.0.4.Final//org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:590)
	at org.jboss.as.server@18.0.4.Final//org.jboss.as.server.Main.determineEnvironment(Main.java:425)
	at org.jboss.as.server@18.0.4.Final//org.jboss.as.server.Main.main(Main.java:97)
	at org.jboss.modules.Module.run(Module.java:353)
	at org.jboss.modules.Module.run(Module.java:321)
	at org.jboss.modules.Main.main(Main.java:604)

On Tue, 2022-01-25 at 17:16 +0100, Jean Francois Denise wrote:
WILDFLY_SERVER_CONFIGURATION should be used. I think you ran into a typo
in the README.
Just curious, what is the quickstart you are trying with openshift that
requires standalone-full.xml?

On 1/25/22 4:12 PM, Manuel Finelli wrote:
Hi Experts,

I had a couple of tries with OpenShift and WildFly to spin up a simple application (the EAP quickstart `cmt`). I installed `crc` [1] to run OpenShift locally and `oc` [2] to control it.

What I tried so far:
* Employ wildfly-centos7 [3] directly and then spin up a new-app with the command `oc new-app https://github.com/wildfly/quickstart.git --context-dir=cmt --image=quay.io/wildfly/wildfly-centos7 --env SERVER_CONFIGURATION=standalone-full.xml`
* Build the WFLY image from "scratch" and then spin up a new-app with the env variable `--env SERVER_CONFIGURATION=standalone-full.xml`...more or less what it is suggested in [4] but adding the env variable, i.e. `oc new-app wildfly-quickstart/cmt -e SERVER_CONFIGURATION=standalone-full.xml` (where wildfly-quickstart is the OpenShift project I am using)

In both cases, I get very close to success but what does not work is `--env SERVER_CONFIGURATION=standalone-full.xml`. My WildFly server gets set up with standalone.xml, which is not enough for my quickstart.
As a side note, I can see `SERVER_CONFIGURATION=standalone-full.xml` among the environment variables of the WFLY pod. I also ran a couple of experiments playing with JAVA_OPTS_APPEND (e.g. `JAVA_OPTS_APPEND=-Djboss.server.default.config=standalone-full.xml`) but it did not help.

So my questions would be:
* Is there a different way to pass env variables when applications are created? If that is the case, would it be worth mentioning it here [5]?
* Have I missed something else?

[1] https://developers.redhat.com/products/codeready-containers/overview
[2] https://access.redhat.com/downloads/content/290/ver=4.9/rhel---8/4.9.17/x86_64/product-software
[3] https://quay.io/repository/wildfly/wildfly-centos7?tab=info
[4] https://github.com/wildfly/wildfly-s2i/tree/master/examples/jsf-ejb-jpa
[5] https://github.com/wildfly/wildfly-s2i/blob/master/README.md#environment-variables-to-be-used-when-running-application
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org

wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org