Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guide: Migrate from WildFly docker image to the builder/runtime images #669

Open
jmesnil opened this issue Oct 10, 2024 · 0 comments
Open
Labels

Comments

@jmesnil
Copy link
Member

jmesnil commented Oct 10, 2024

We have many users that use https://github.com/jboss-dockerfiles/wildfly as the base image where they can drop their deployments.

However some new features of WildFly are only available as Galleon feature packs (Keycloak SAML adapter, gRPC, datasources), this image is not ideal to provision them on top of the base WildFly server.

We could create a guide that helps use move from the WildFly Docker image to the builder/runtime image.
The guide would explain the differences between the 2 architectures and shows how users can achieve the same application image from one architecture to another.
Then, the guide would show how you can simply add a feature pack to WildFly (eg Keycloal SAML adapter) by tweaking the Containerfile
Finally, for users that are in control of the deployment source code, we should mention that the wildfly-maven-plugin is able to generated an application image from their Maven pom.xml directly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

1 participant