management-interface | A UI to manage multi tenancy

I found out the PID of applications that were using those ports and used kill -9 PID. It worked.

This is because during the initial boot a logging.properties file is used to configure the log manager until the logging subsystem is activated. There are two options.

1. You copy an already configured logging.properties and standalone-ha.xml over to your image.
2. In a RUN command in your Dockerfile configure logging by starting the server, then executing the CLI script.

You actually don't need to install that module to achieve this. WildFly has a built-in json-formatter and socket-handler. In fact a lot of the code looks like it was taken from the JBoss Log Manager :) The one difference is the fields. With the below example I'll just show you an option you can use.

Ports of different pods may collide only if you use hostPort or hostNetwork. Otherwise, you shouldn't encounter any issues while running multiple identical pods in the same node.

You can just try to run the following commands. Your Wildfly pods should run without any issues because the ports they use are inside the containers.

You need to locate the jar file providing these annotation classes and add it to the Module Dependencies.

If your project is Gradle or Maven managed, add the dependency to build.gradle/pom.xml instead.

You need to add the wildfly-maven-plugin in the configuration

The issue was indeed that I was using the wrong python version to run the pmg-script (It was a work computer with many different python versions and I was using python 3.7.6 but there was an old python 2.7 set as default which was used when jus ran "python pmg"). I ran conda activate base in my /home/username/anaconda3 and then python pmg etc. and it worked.

After rebuilding the cluster the DEBUG logs started to come through and so did more error messages.

The problem turned out to be an SSL issue Establishing SSL connection without server's identity verification is not recommended.

I have added this to the keycloak env

Wildfly uses Undertow as its Servlet container and you have a dependency on Spring Boot’s Undertow starter. As a result there are two different versions of Undertow’s classes available. As you suspected, these two versions are conflicting and causing a failure.

If you are only deploying your application to Wildfly, you can remove the dependency on spring-boot-starter-undertow entirely. If you want to be able to run your app outside Wildfly using embedded Undertow, you should mark the dependency on spring-boot-starter-undertow as provided.