jboss-dockerfiles / drools Goto Github PK

View Code? Open in Web Editor NEW

61.0 61.0 98.0 174 KB

License: MIT License

Shell 63.46% Dockerfile 36.54%

drools's People

Contributors

Stargazers

Watchers

Forkers

isaacueca alex-dixon jstrittmatter sunnytam joseluis901 ansgarkroger hfcalmeida rycaon30 nanki dinadaftedar alucardpj lhwong patrickcharlier-github heavenn goalltheway mbiarnes zahid wpetit laimismilas kesuskim zengxijin mcimbora tarilabs cletuslee keyang aabusharekh jian-feng mailkatta romartin blofroth wiktorn spiros76 suthakar123 nestaway finkky kouweizhong johnbouma shivanshgaur jmgsquared214 ruchikagupta12 xiaoruiguo rohit-zabbed erbrito ally-jarrett revkov jmarlonsf spantree gusdelact marianbuenosayres jvbrandaom danilodeluca pymma jkzang artootrills mareknovotny bitwise-shubhamk pushkar-bitwise dchristm77 zdjkea cristianonicolai lumeloc navinpassionbiz tyyzqmf qiudaoke bogdanrudka leandrolonardoni lalonardoni pasta-83 technicalengineer tomcent-tom gizmocoder aldokkani windillusion xuze1993 evolonman108 sgrichards rudrarb1 andersongomesu emcrisostomo vebsun code4dc moayyaed mehaksika tasmot ida-namida viethapascal jxs-kie l86400 jean-francoistremblaytelus cgb-lowcode wolwire cgb-ruleengine drewbrim jespinoz lordcodyody salimsayed erdosam alexgrig1

drools's Issues

Support for docker-compose network when linking kie-server with workbench

It would be nice to have kie-server-showcase linked with the workbench using only docker networks and docker-compose. The --link docker feature is deprecated and if using via docker-compose, you don't get the expected variables to be injected in the container.

I would like to have one docker-compose with both kie-server and the workbench talking to each other in the same docker network.

See: https://docs.docker.com/compose/link-env-deprecated/

the current image does not support non western character sets

could u add -Dfile.encoding=UTF-8 to JAVA_OPTS? Because this is not convenient for native speakers of non English speaking countries.

Automatic KIE Server Configuration Not Compatible With Docker Compose 2+

I am testing integration between jBPM Workbench Showcase and KIE Server Showcase Docker images. I followed the instructions and ran:

docker run -p 8080:8080 -p 8001:8001 -d --name jbpm-workbench jboss/jbpm-workbench-showcase:latest
docker run -p 8081:8080 -d --name kie-server --link jbpm-workbench:kie_wb jboss/kie-server-showcase:6.5.0.Final

This works great!

However, using docker-compose.yml at v2, this does not work. I have both workbench and kieserver subdirectories with Dockerfiles that simply extend the public images. I have not customized the images yet.

version: '2'
services:
workbench:
build: './workbench'
ports:
- "8080:8080"
kieserver:
build: './kieserver'
links:
- workbench:kie_wb
ports:
- "8081:8080"

Further research into docker compose says this is not a bug even though it breaks backward compatibility:
docker/compose#2172
docker/compose#2038

Here is a v1 docker-compose.yml which works correctly:

workbench:
build: './workbench'
ports:
- "8080:8080"
kieserver:
build: './kieserver'
links:
- workbench:kie_wb
ports:
- "8081:8080"

It seems that the auto-configure is based on the host name, however, this will not work in future versions of docker-compose because it uses DNS instead. My suggestion would be to improve the "auto-discovery" feature so it is less dependent on certain implementations. Perhaps an environment variable with the host name might suffice but then, the host name might not be available if the workbench hostname is set dynamically so some other discovery tool/technique might be needed.

With jBPM 7 coming out, I hope maybe this can be addressed since there is even more emphasis on this controller/executor pattern. It has a lot of potential!

Readme should suggest alternate user/roles options

As always, thanks for the Docker containers! Very helpful!

I would like to suggest adding some alternative options for configuring users and roles. My understanding is that jBPM is delegating this to Wildfly but that one could also write a UserGroupCallback which I think needs to go in the jBPM WAR.

My goal is to configure against a database. This seems easier with Wildfly config than with the UserGroupCallback. I have found an example for pointing standalone.xml to a database within a security-domain but nothing regarding security-realms. I have not found a lot of information about how jBPM relies on security-realms versus security-domains but from the Readme, it appears to rely on both. I assume life would be easier if we were using LDAP but in my case, LDAP is not a reliable source of role information.

Any recommendations are appreciated and I will try my best to post back any updates I find!

Communication issue between drools-workbench-showcase and kie-server-showcase

I'm working with tag 7.15.0.Final.

Running both docker images with the following commands:

Drools Workbench Showcase

docker run -p 8080:8080 -p 8001:8001 -d --name drools-workbench jboss/drools-workbench-showcase:7.15.0.Final

Kie Server Showcase

docker run -p 8180:8080 -d --name kie-server --link drools-workbench:kie-wb jboss/kie-server-showcase:7.15.0.Final

Everything works find until I try to access the Manage options.

Looking at the logs of the kie-server-showcase container, I'm not seeing anything.

Looking at the logs of the jbpm-workbench-showcase container I get:

31m20:36:15,320 ERROR [org.dashbuilder.exception.ExceptionManager] (default task-2) Can't lookup on specified data set: jbpmProcessInstances: org.dashbuilder.dataset.exception.DataSetLookupException: C
an't lookup on specified data set: jbpmProcessInstances
        at org.dashbuilder.dataset.DataSetManagerImpl.lookupDataSet(DataSetManagerImpl.java:156)
        at org.dashbuilder.dataset.DataSetManagerCDI$Proxy$_$$_WeldClientProxy.lookupDataSet(Unknown Source)
        at org.dashbuilder.dataset.service.DataSetLookupServicesImpl.lookupDataSet(DataSetLookupServicesImpl.java:78)
        at org.dashbuilder.dataset.service.DataSetLookupServicesImpl$Proxy$_$$_WeldClientProxy.lookupDataSet(Unknown Source)
        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:498)
        at org.jboss.errai.bus.server.io.AbstractRPCMethodCallback.invokeMethodFromMessage(AbstractRPCMethodCallback.java:65)
        at org.jboss.errai.bus.server.io.ValueReplyRPCEndpointCallback.callback(ValueReplyRPCEndpointCallback.java:40)
        at org.jboss.errai.bus.server.io.RemoteServiceCallback.callback(RemoteServiceCallback.java:54)
        at org.jboss.errai.cdi.server.CDIExtensionPoints$2.callback(CDIExtensionPoints.java:448)
        at org.jboss.errai.bus.server.DeliveryPlan.deliver(DeliveryPlan.java:47)
        at org.jboss.errai.bus.server.ServerMessageBusImpl.sendGlobal(ServerMessageBusImpl.java:297)
        at org.jboss.errai.bus.server.SimpleDispatcher.dispatchGlobal(SimpleDispatcher.java:46)
        at org.jboss.errai.bus.server.service.ErraiServiceImpl.store(ErraiServiceImpl.java:96)
        at org.jboss.errai.bus.server.service.ErraiServiceImpl.store(ErraiServiceImpl.java:113)
        at org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.doPost(DefaultBlockingServlet.java:144)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:706)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:791)
        at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
        at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
        at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:173)
        at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
        at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
        at org.uberfire.ext.security.server.SecureHeadersFilter.doFilter(SecureHeadersFilter.java:110)
        at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
        at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
        at org.uberfire.ext.security.server.SecurityIntegrationFilter.doFilter(SecurityIntegrationFilter.java:70)
        at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
        at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
        at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
        at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
        at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68)
        at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
        at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
        at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132)
        at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
        at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
        at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
        at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
        at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
        at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
        at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
        at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
        at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
        at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
        at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
        at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
        at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
        at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
        at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
        at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
        at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
        at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
        at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
        at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
        at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
        at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
        at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
        at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
        at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
        at java.lang.Thread.run(Thread.java:748)
Caused by: org.kie.server.common.rest.KieServerHttpRequestException: Unable to retrieve input stream of response
        at org.kie.server.common.rest.KieServerHttpRequest.responseStream(KieServerHttpRequest.java:1389)
        at org.kie.server.common.rest.KieServerHttpRequest.responseBuffer(KieServerHttpRequest.java:1407)
        at org.kie.server.common.rest.KieServerHttpRequest.responseBody(KieServerHttpRequest.java:1349)
        at org.kie.server.common.rest.KieServerHttpRequest.access$2100(KieServerHttpRequest.java:117)
        at org.kie.server.common.rest.KieServerHttpRequest$5.body(KieServerHttpRequest.java:1315)
        at org.kie.server.client.impl.AbstractKieServicesClientImpl.createExceptionForUnexpectedResponseCode(AbstractKieServicesClientImpl.java:615)
        at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpPostRequestAndCreateCustomResponse(AbstractKieServicesClientImpl.java:320)
        at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpPostRequestAndCreateCustomResponse(AbstractKieServicesClientImpl.java:300)
        at org.kie.server.client.impl.QueryServicesClientImpl.query(QueryServicesClientImpl.java:1004)
        at org.jbpm.workbench.ks.integration.KieServerDataSetProvider.performQuery(KieServerDataSetProvider.java:257)
        at org.jbpm.workbench.ks.integration.KieServerDataSetProvider.lookupDataSet(KieServerDataSetProvider.java:179)
        at org.jbpm.workbench.ks.integration.KieServerDataSetProvider$Proxy$_$$_WeldClientProxy.lookupDataSet(Unknown Source)
        at org.dashbuilder.dataset.DataSetManagerImpl.lookupDataSet(DataSetManagerImpl.java:154)
        ... 74 more
Caused by: java.net.HttpRetryException: cannot retry due to server authentication, in streaming mode
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1692)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
        at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
        at org.kie.server.common.rest.KieServerHttpRequest.responseCode(KieServerHttpRequest.java:1329)
        at org.kie.server.common.rest.KieServerHttpRequest.post(KieServerHttpRequest.java:719)
        at org.kie.server.client.impl.AbstractKieServicesClientImpl$6.doOperation(AbstractKieServicesClientImpl.java:308)
        at org.kie.server.client.impl.AbstractKieServicesClientImpl.invoke(AbstractKieServicesClientImpl.java:804)
        at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpPostRequestAndCreateCustomResponse(AbstractKieServicesClientImpl.java:305)
        ... 80 more

if I access directly through the browser to the REST API I get access with default credentials:
kieserver/kieserver1!, also with admin/admin.

I'm running the docker in Ubuntu 16.04, with Docker version 18.06.1-ce, build e68fc7a

Where is your docker file?

I am trying to find it to see how to customize https://registry.hub.docker.com/u/jboss/drools-workbench/

Found Error when clone ssh

I have found error when I call command : git clone ssh://admin@localhost:8001/uf-playground

response : Cloning into 'uf-playground'...
Password authentication
Password:
Can't resolve repository name.fatal: Could not read from remote repository.

But, I use password : admin, to authen. Please help to resolve it.

get Forbidden

i follow the instructions to install KIE Server showcase:
after execute command docker run -p 8180:8080 -d --name kie-server --link drools-wb:kie_wb jboss/kie-server-showcase:latest
the "drools-wb" is the name of my container that i run it with below command:
docker run -p 8080:8080 -p 8001:8001 -d --name drools-wb jboss/drools-workbench-showcase:latest

and container log is ok as below:

INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 52946ms - Started 847 of 1114 services (397 services are lazy, passive or on-demand)

in browser when i try http://my-ip:8180/kie-server/ get Forbidden. what is that damn thing?
how can i fix that?
actually i first run drools-workbench-showcase and then start kie-server-showcase .is that true?

Missing rest-all role

As described here
http://mswiderski.blogspot.com.es/2015/09/unified-kie-execution-server-part-3.html
In the kie-server showcase image is missing the assigned role "rest-all" for the default user kie-server.

Check the discussion here https://groups.google.com/forum/m/?utm_medium=email&utm_source=footer#!msg/drools-setup/4v6xhh0qFyU/glazhmisBAAJ

OCI runtime create failed

Hello!

after add pvc in k8s:

volumeMounts:
- mountPath: "/opt"
name: storage
volumes:
- name: storage
persistentVolumeClaim:
claimName: drools-pvc

I get error:
OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "./start_business-central-wb.sh": stat ./start_business-central-wb.sh: no such file or directory": unknown

How can I start service in k8s with persistentVolumeClaim? Whithout it works fun.

Docker Images are too big

First, let me just say thank you for creating these, they are awesome!

One thing that stood out to me was the time it took to download the images. I have a process where I need to transfer these offline and that can be more cumbersome (I realize I'm in a minority for that part).

That said, that indicates to me that there might be a better way. Has there been any effort into running this with Wildfly Swarm or some other lightweight solution?

how to config docker drools-wb M2_HOME

For help：how to config docker drools-wb M2_HOME？

Add wait-for-it to the kie-server image.

Hello,

as I understand the kie-server must be always run after the drools-workbench is up and running. This means that we can't use docker-compose because docker-compose starts both of the images simultaneously. What docker suggests is to use tools such as wait-for-it.sh:

https://docs.docker.com/compose/startup-order/

I tried to do that but it says the kie-server does not have it installed. Can you please provide it? This would make possible to use docker-compose.

Thank you.

Support Apple Silicon (M1)

I've just started drools-wb and kie-server on M1 with this docker-compose.yml

version: '3'

services:
  drools-wb:
    container_name: drools-wb
    image: jboss/drools-workbench-showcase:latest
    ports:
      - 8001:8001
      - 28080:8080

  kie-server:
    container_name: kie-server
    image: jboss/kie-server-showcase:latest
    links:
      - drools-wb:kie_wb
    ports:
      - 8080:8080
    depends_on:
      - drools-wb
    environment:
      # KIE Workbench environment variables
      # Neccessary to connect the KIE server to the KIE workbench
      - KIE_WB_PORT_8080_TCP=tcp://kie_wb:8080
      - KIE_WB_ENV_KIE_CONTEXT_PATH=drools-wb
      - KIE_WB_PORT_8080_TCP_ADDR=kie_wb

Got this error.

drools-wb   | =========================================================================
drools-wb   |
drools-wb   | 15:41:05,187 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final
drools-wb   | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
kie-server  | Using 'kie-server-9b1099bf9020' as KIE server identifier
drools-wb   | *** JBossAS process (133) received SEGV signal ***
kie-server  | Detected successful link for KIE Workbench container. Applying automatic configuration for the link...
kie-server  | Using 'http://172.20.0.3:8080/kie-server/services/rest/server' as KIE server location
kie-server  | Using 'http://kie_wb:8080/drools-wb/rest/controller' as KIE server controller
kie-server  | Using 'http://kie_wb:8080/drools-wb/maven2' for the kie-workbench Maven repository URL
kie-server  | Running KIE Execution Server on JBoss Wildfly...
kie-server  | JAVA_OPTS already set in environment; overriding default settings with values: -Xms256m -Xmx1024m -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8
kie-server  | =========================================================================
kie-server  |
kie-server  |   JBoss Bootstrap Environment
kie-server  |
kie-server  |   JBOSS_HOME: /opt/jboss/wildfly
kie-server  |
kie-server  |   JAVA: /usr/lib/jvm/java/bin/java
kie-server  |
kie-server  |   JAVA_OPTS:  -server -Xms256m -Xmx1024m -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8  --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
kie-server  |
kie-server  | =========================================================================
kie-server  |
drools-wb exited with code 0
kie-server  | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
kie-server  | *** JBossAS process (222) received SEGV signal ***

I believe it has something to do with this known issue from Docker https://docs.docker.com/docker-for-mac/apple-silicon/#known-issues

Please consider supporting M1

Forbidden when running on AWS

I configured this to run through Elastic Beanstalk however when I log in I get forbidden. Any idea why?

Adding new user to workbench via drools-users.properties

Hello,
I'm trying to add new users via drools-users.properties file, but something is wrong.
You can check my forked repository to get the diff code or follow as bellow.
Some considerations:

When I login into workbench with user "admin" and check the users list, my new user "xablau" exists.
Using the user "admin" if I change the xablau's password then I try to login works!

diff --git a/etc/drools-roles.properties b/etc/drools-roles.properties
index d9f91c5..51613de 100644
--- a/etc/drools-roles.properties
+++ b/etc/drools-roles.properties
@@ -1,4 +1,5 @@
 admin=admin,analyst,kiemgmt,rest-all
+xablau=admin,analyst,kiemgmt,rest-all
 krisv=admin,analyst
 john=analyst,Accounting,PM
 sales-rep=analyst,sales
diff --git a/etc/drools-users.properties b/etc/drools-users.properties
index 7c7a308..986227e 100644
--- a/etc/drools-users.properties
+++ b/etc/drools-users.properties
@@ -1,5 +1,6 @@
 #admin=admin
 admin=207b6e0cc556d7084b5e2db7d822555c
+xablau=207b6e0cc556d7084b5e2db7d822555c
 
 #krisv=krisv
 krisv=7b21a03b9918f9c629a46e119a9b8714

jboss/kie-server latest tag pointing to the wrong version on docker hub

https://hub.docker.com/r/jboss/kie-server/tags

The latest tag is pointing to 7.15.0.Final and should be pointing to 7.17.0.Final.

Not sure you want to fix that but wanted to report it just in case.

Drools workbench exites when I start kie sv

Drools workbench exites on docker when I run Kie. My configuration is what is on documentation.

First I run:
docker run -p 8080:8080 -p 8001:8001 -d --name drools-workbench jboss/drools-workbench-showcase:latest

then
docker run -p 8180:8080 -d --name kie-server --link drools-wb:kie-wb jboss/kie-server-showcase:latest

docker logs says:

05:08:56,803 WARN [org.jboss.as.jaxrs] (MSC service thread 1-3) WFLYRS0018: Explicit usage of Jackson annotation in a JAX-RS deployment; the system will disable JSON-B processing for the current deployment. Consider setting the 'resteasy.preferJacksonOverJsonB' property to 'false' to restore JSON-B.

05:08:56,814 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

05:08:56,816 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)

05:08:56,821 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.4)

05:08:56,824 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.mariadb.jdbc.Driver (version 1.3)

05:08:56,966 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Estrella Galicia' 9.3.1.Final

05:08:56,988 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 3.0.5 (Final)

05:08:57,262 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = drools-wb.war_org.postgresql.Driver_9_4

05:08:57,262 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = drools-wb.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1

05:08:57,263 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = drools-wb.war_org.mariadb.jdbc.Driver_1_3

05:08:57,264 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = drools-wb.war_com.mysql.jdbc.Driver_5_1

05:08:58,835 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) WFLYCLINF0002: Started client-mappings cache from ejb container

05:08:59,455 INFO [org.wildfly.security] (MSC service thread 1-4) ELY00001: WildFly Elytron version 1.6.0.Final

05:09:00,308 INFO [org.jboss.weld.Event] (MSC service thread 1-3) WELD-000411: Observer method [BackedAnnotatedMethod] org.uberfire.ext.security.server.HttpServletRequestProducerExtension.processAnnotatedType(@Observes ProcessAnnotatedType<X>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.

05:09:00,676 INFO [org.jboss.weld.Event] (MSC service thread 1-3) WELD-000411: Observer method [BackedAnnotatedMethod] public org.jboss.errai.security.server.SecurityAnnotationExtension.addParameterLogger(@Observes ProcessAnnotatedType<?>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.

05:09:00,687 INFO [org.jboss.weld.Event] (MSC service thread 1-3) WELD-000411: Observer method [BackedAnnotatedMethod] public org.jboss.errai.cdi.server.CDIExtensionPoints.observeResources(@Observes ProcessAnnotatedType<T>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.

05:09:00,945 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-3) starting errai cdi ...

05:09:01,722 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 5) WELD-000119: Not generating any bean definitions from org.kie.workbench.common.stunner.core.util.Buttons$Builder because of underlying class loading error: Type org.gwtbootstrap3.client.ui.Button from [Module "deployment.drools-wb.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.

05:09:01,866 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000119: Not generating any bean definitions from org.kie.workbench.common.stunner.core.util.DropDownMenus$Builder because of underlying class loading error: Type org.gwtbootstrap3.client.ui.DropDownMenu from [Module "deployment.drools-wb.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.

05:09:01,871 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 4) WELD-000119: Not generating any bean definitions from org.kie.workbench.common.stunner.core.util.ButtonGroups$Builder because of underlying class loading error: Type com.google.gwt.user.client.ui.Widget from [Module "deployment.drools-wb.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.

05:09:01,876 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 4) WELD-000119: Not generating any bean definitions from org.kie.workbench.common.stunner.core.util.AnchorListItems$Builder because of underlying class loading error: Type org.gwtbootstrap3.client.ui.AnchorListItem from [Module "deployment.drools-wb.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.

Support for docker swarm

Would like to deploy the workbench in a swarm which means we need to persist the data. Any recommendation on how we do it give we have a persistent storage available across all the host in the swarm

Dockerhub documentation says link to workbench should be kie_wb, but in reality, it should be kie-wb

took me hours/days to discover this :-(

./start_kie-server.sh: line 12: ip: command not found

In kie-server-showcase, the base image centos:7 does not contain "ip" command, so it cannot fetch the local ip address, the kie server location will be:

Using 'http://:8080/kie-server/services/rest/server' as KIE server location

Unable to mount host directory

I'm running docker 1.11.1
I've been trying to get the git directory to store on my host, so that all my rules don't disappear every time the container restarts, but I keep coming back to this error.

I've tried with VOLUME, with docker run -v /dir:/dir, with docker run -v container:/dir, with --volumes-from ... it doesn't matter. The files do end up under /var/lib/docker/volumes on my host, but not in the host directory I specified, and whenever it looks identical to a working example, it ends up back at this error, or, with the error here: https://gist.github.com/ge0ffrey/8e69c04dd8f619480fc9

Can someone please provide a working example that allows the user to move the git repo out of the container, and onto a host, or a persistent volume?

Thanks

17:23:25,499 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "drools-wb.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"drools-wb.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"drools-wb.war\".WeldStartService: Failed to start service
    Caused by: org.jboss.weld.exceptions.DeploymentException: Exception List with 1 exceptions:
Exception 0 :
org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void org.kie.workbench.drools.backend.server.AppSetup.assertPlayground() on org.kie.workbench.drools.backend.server.AppSetup@7dab7868
        at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
        at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
        at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
        at org.jboss.weld.injection.producer.BeanInjectionTarget.postConstruct(BeanInjectionTarget.java:70)
        at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
        at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
        at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
        at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
        at org.kie.workbench.drools.backend.server.AppSetup$Proxy$_$$_WeldClientProxy.toString(Unknown Source)
        at org.uberfire.backend.server.cdi.SystemConfigProducer.runPostConstruct(SystemConfigProducer.java:160)
        at org.uberfire.backend.server.cdi.SystemConfigProducer.afterDeploymentValidation(SystemConfigProducer.java:143)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90)
        at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271)
        at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
        at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258)
        at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237)
        at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174)
        at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133)
        at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107)
        at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
        at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:35)
        at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28)
        at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:439)
        at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:90)
        at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98)
        ... 33 more
Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void org.guvnor.structure.backend.config.ConfigurationServiceImpl.setup() on org.guvnor.structure.backend.config.ConfigurationServiceImpl@641098fa
        at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
        at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
        at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
        at org.jboss.weld.injection.producer.BeanInjectionTarget.postConstruct(BeanInjectionTarget.java:70)
        at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:153)
        at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
        at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
        at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
        at org.guvnor.structure.backend.config.ConfigurationServiceImpl$Proxy$_$$_WeldClientProxy.endBatch(Unknown Source)
        at org.kie.workbench.drools.backend.server.AppSetup.assertPlayground(AppSetup.java:197)
        ... 38 more
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98)
        ... 47 more
Caused by: java.lang.RuntimeException: Could not resolve 'systemFS' main root directory.
        at org.guvnor.structure.backend.config.ConfigurationServiceImpl.setup(ConfigurationServiceImpl.java:130)
        ... 52 more