You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the docker images, but one thing I can't change is the server name from defaultServer? as for logging when running multiple images of different applications they are all showing as defaultServer. It shows the application name correctly as it runs that
This is the current way we create an image FROM open-liberty:23.0.0.6-kernel-slim-java11-openj9 ENV KEYSTORE_REQUIRED=false VERBOSE=true EXPOSE 8080 8543 COPY --chown=1001 dependencies /opt/ol/wlp/usr/ COPY --chown=1001 config /config/ #this has the server.xml and a folder called apps, which as the war file COPY --chown=1001 keystore /var/keystore/ RUN features.sh RUN configure.sh
Am I doing it correctly? I can provide more information if needed
The text was updated successfully, but these errors were encountered:
@lancechant The default server name has many references within the Liberty images (symlinks, startup process, permission settings, server cache, etc) and it's not customizable at the moment. But it's in our roadmap to support. We don't have a timeline to share at this time. Related issue: #284
Hi
We are using the docker images, but one thing I can't change is the server name from defaultServer? as for logging when running multiple images of different applications they are all showing as defaultServer. It shows the application name correctly as it runs that
This is the current way we create an image
FROM open-liberty:23.0.0.6-kernel-slim-java11-openj9 ENV KEYSTORE_REQUIRED=false VERBOSE=true EXPOSE 8080 8543 COPY --chown=1001 dependencies /opt/ol/wlp/usr/ COPY --chown=1001 config /config/ #this has the server.xml and a folder called apps, which as the war file COPY --chown=1001 keystore /var/keystore/ RUN features.sh RUN configure.sh
Am I doing it correctly? I can provide more information if needed
The text was updated successfully, but these errors were encountered: