Dockerfile start jboss cli не работает

Я хочу запустить сценарий docker-cli.sh на Wildfly.

FROM jboss/wildfly:10.0.0.Final

COPY maven/config /opt/jboss/wildfly/standalone/configuration/
COPY maven/deployments /opt/jboss/wildfly/standalone/deployments/
COPY maven/postgres-module /opt/jboss/wildfly/modules/org/postgresql/main/

RUN mkdir -p wildfly/modules/org/postgresql/main

RUN wildfly/bin/add-user.sh admin admin --silent

RUN wildfly/bin/jboss-cli.sh --connect --controller=localhost:9990


CMD ["wildfly/bin/standalone.sh","-b","0.0.0.0","-bmanagement", "0.0.0.0"]

Это мой файл докеров. Если я хочу построить его с помощью (https://github.com/fabric8io/docker-maven-plugin) mvn docker: build, я столкнулся со следующей ошибкой:

Команда wildfly / bin / jboss-cli.sh --connect --controller = localhost: 9990 вернула ненулевой код: 1 -> [Help 1]

Но если я прокомментирую вторую последнюю строчку и выполню ее, она работает.

Если я после запуска контейнера подключусь к docker cli с помощью Kitemanic, я могу выполнить этот шаг скрипта.

Журнал ошибок:

[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.21.0:build (default-cli) on project country_service: Unable to build image [company_service] : The command 'wildfly/bin/jboss-cli.sh --connect --controller=localhost:9990' returned a non-zero code: 1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.fabric8:docker-maven-plugin:0.21.0:build (default-cli) on project country_service: Unable to build image [company_service] : The command 'wildfly/bin/jboss-cli.sh --connect --controller=localhost:9990' returned a non-zero code: 1
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:497)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build image [company_service] : The command 'wildfly/bin/jboss-cli.sh --connect --controller=localhost:9990' returned a non-zero code: 1
        at io.fabric8.maven.docker.AbstractDockerMojo.execute(AbstractDockerMojo.java:226)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
        ... 20 more
Caused by: io.fabric8.maven.docker.access.DockerAccessException: Unable to build image [company_service] : The command 'wildfly/bin/jboss-cli.sh --connect --controller=localhost:9990' returned a non-zero code: 1
        at io.fabric8.maven.docker.access.hc.DockerAccessWithHcClient.buildImage(DockerAccessWithHcClient.java:220)
        at io.fabric8.maven.docker.service.BuildService.doBuildImage(BuildService.java:160)
        at io.fabric8.maven.docker.service.BuildService.buildImage(BuildService.java:124)
        at io.fabric8.maven.docker.service.BuildService.buildImage(BuildService.java:60)
        at io.fabric8.maven.docker.BuildMojo.buildAndTag(BuildMojo.java:58)
        at io.fabric8.maven.docker.BuildMojo.executeInternal(BuildMojo.java:44)
        at io.fabric8.maven.docker.AbstractDockerMojo.execute(AbstractDockerMojo.java:223)
        ... 22 more
Caused by: io.fabric8.maven.docker.access.DockerAccessException: The command 'wildfly/bin/jboss-cli.sh --connect --controller=localhost:9990' returned a non-zero code: 1
        at io.fabric8.maven.docker.access.chunked.BuildJsonResponseHandler.process(BuildJsonResponseHandler.java:25)
        at io.fabric8.maven.docker.access.chunked.EntityStreamReaderUtil.processJsonStream(EntityStreamReaderUtil.java:26)
        at io.fabric8.maven.docker.access.hc.DockerAccessWithHcClient$HcChunkedResponseHandlerWrapper.handleResponse(DockerAccessWithHcClient.java:652)
        at io.fabric8.maven.docker.access.hc.ApacheHttpClientDelegate$StatusCodeCheckerResponseHandler.handleResponse(ApacheHttpClientDelegate.java:172)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:222)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:164)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:139)
        at io.fabric8.maven.docker.access.hc.ApacheHttpClientDelegate.post(ApacheHttpClientDelegate.java:102)
        at io.fabric8.maven.docker.access.hc.DockerAccessWithHcClient.buildImage(DockerAccessWithHcClient.java:218)
        ... 28 more


docker maven dockerfile docker-for-windows jboss
person J. Doe    schedule 11.08.2017    source источник
comment
Не могли бы вы опубликовать результат docker logs для этого контейнера?   -  person Fotis    schedule 11.08.2017
comment
@Fotis добавляю журнал ошибок   -  person J. Doe    schedule 11.08.2017

Ответы (1)


arrow_upward
0
arrow_downward

Нашел хорошее решение (от товарища по команде):

<run>
	<ports>
		<port>8080:8080</port>
		<port>9990:9990</port>
	</ports>
	<extraHosts>
   			<extraHost>my_db_postgress:192.168.99.100</extraHost>
	</extraHosts>
</run>

Я добавил в конфигурацию запуска дополнительный хост и добавил его в свой standalone.xml

person J. Doe    schedule 11.08.2017