[jboss-jira] [JBoss JIRA] (WFCORE-3937) Error when running configured wildfly

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594240#comment-13594240 ] 

Brian Stansberry commented on WFCORE-3937:
------------------------------------------

The problem is the 'docker build' is creating the standalone_xml_history because it is modifying the config:

```
y$ docker build -t testing .
Sending build context to Docker daemon  3.026MB
Step 1/2 : FROM jboss/wildfly:13.0.0.Final at sha256:5d667ce3a423eb0402d33730d2ceb6286bc2e245d187baeccda197d562f70508
sha256:5d667ce3a423eb0402d33730d2ceb6286bc2e245d187baeccda197d562f70508: Pulling from jboss/wildfly
469cfcc7a4b3: Already exists 
05677e4d61f0: Pull complete 
a9520f492457: Pull complete 
4d201219d6b1: Pull complete 
ea67bbe40b46: Pull complete 
Digest: sha256:5d667ce3a423eb0402d33730d2ceb6286bc2e245d187baeccda197d562f70508
Status: Downloaded newer image for jboss/wildfly:13.0.0.Final at sha256:5d667ce3a423eb0402d33730d2ceb6286bc2e245d187baeccda197d562f70508
 ---> be0490eb815b
Step 2/2 : RUN ./wildfly/bin/jboss-cli.sh "embed-server --std-out=echo,   /system-property=ee8.preview.mode:add(value=true)"
 ---> Running in 292ca65b3250
06:26:29,382 INFO  [org.jboss.modules] (CLI command executor) JBoss Modules version 1.8.5.Final
06:26:29,450 INFO  [org.jboss.msc] (CLI command executor) JBoss MSC version 1.4.2.Final
06:26:29,462 INFO  [org.jboss.threads] (CLI command executor) JBoss Threads version 2.3.2.Final
06:26:29,659 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) starting
06:26:31,279 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
06:26:31,309 INFO  [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.3.3.Final
06:26:31,366 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
06:26:31,512 INFO  [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
06:26:31,529 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/jboss/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
06:26:31,629 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
06:26:31,631 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) started in 2241ms - Started 66 of 80 services (25 services are lazy, passive or on-demand)
{"outcome" => "success"}
06:26:32,244 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0050: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) stopped in 18ms
 ---> a0c206670dde
Removing intermediate container 292ca65b3250
Successfully built a0c206670dde
Successfully tagged testing:latest
```

Solution is to clean that up in the Dockerfile:

```
FROM jboss/wildfly:13.0.0.Final at sha256:5d667ce3a423eb0402d33730d2ceb6286bc2e245d187baeccda197d562f70508
RUN ./wildfly/bin/jboss-cli.sh "embed-server --std-out=echo, \
  /system-property=ee8.preview.mode:add(value=true)"
RUN rm -rf ./wildfly/standalone/configuration/standalone_xml_history
```

[~jmesnil] Perhaps server boot should include a --no-history option and the CLI embed-server command could expose that as a param in order to make it easier to do this kind of thing.  (N.B.  --read-only-server-config and --no-history would conflict somewhat, as without history things like reload cannot work with a --read-only-server-config server.)

> Error when running configured wildfly
> -------------------------------------
>
>                 Key: WFCORE-3937
>                 URL: https://issues.jboss.org/browse/WFCORE-3937
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Management
>    Affects Versions: 5.0.0.Final
>            Reporter: Stephen Buergler
>            Assignee: Jeff Mesnil
>            Priority: Minor
>         Attachments: Dockerfile
>
>
> 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
> ...
> 08:50:08,531 WARN  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot.
> To reproduce:
> docker build -t testing .
> docker run --rm -it testing



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)