-
Notifications
You must be signed in to change notification settings - Fork 5
Example: Using GlassFish Server with the docker Command
Run GlassFish with the following command. Ports 4848 and 8080 inside the container will be mapped to the host.
docker run -p 8080:8080 -p 4848:4848 ghcr.io/eclipse-ee4j/glassfish
Or with a command for a specific tag (GlassFish version or alias latest):
docker run -p 8080:8080 -p 4848:4848 ghcr.io/eclipse-ee4j/glassfish:latest
Open the following URLs in the browser:
- Welcome screen: http://localhost:8080
-
Administration Console: https://localhost:4848 - log in using
admin/admin(User name/Password)
Stop GlassFish with the following command:
docker stop CONTAINER_ID
CONTAINER_ID can be found from the output of the following command:
docker ps
If you are experimenting just on your local machine, you can also just press CTRL+C or use the SIGTERM signal.
You can run an application located in your filesystem with GlassFIsh in a Docker container.
Follow these steps:
- Create an empty directory on your filesystem, e.g.
/deployment - Copy the application package to this directory - so that it's for example on the path
/deployment/application.war - Run the following command to start GlassFish in Docker with your application, where
/deploymentsis path to the directory created in step 1:
docker run -p 8080:8080 -p 4848:4848 -v /deployments:/opt/glassfish7/glassfish/domains/domain1/autodeploy glassfish
Then you can open the application in the browser with:
The context root (application) is derived from the name of the application file (e.g. application.war would deployed under the application context root). If your application file has a different name, please adjust the contest root in the URL accordingly.
You can modify the start command of the Docker container to startserv --debug to enable debug mode. You should also map the debug port 9009.
docker run -p 9009:9009 -p 8080:8080 -p 4848:4848 glassfish startserv --debug
Then connect your debugger to the port 9009 on localhost.
If you need suspend GlassFish startup until you connect the debugger, use the --suspend argument instead:
docker run -p 9009:9009 -p 8080:8080 -p 4848:4848 glassfish startserv --suspend
The following environment variables can be set to configure GlassFish Server:
-
AS_ADMIN_MASTERPASSWORD- to change the default master password -
AS_ADMIN_PASSWORD- to change the default admin password
The following environment variables are read-only and can be used in derived Docker images or scripts:
-
AS_PASSWORD_FILE- path to the password file with the admin password. It's applied by default to any asadmin command -
AS_ADMIN_USER- name of the admin user. It's applied by default to any asadmin command -
PATH_GF_HOME- directory of the GlassFish installation. Also the default working directory -
PATH_GF_SERVER_LOG- path to the server log file
It's possible to specify custom commands to run in the Docker container before GlassFish server starts. The following methods are supported:
-
${PATH_GF_HOME}/custom/init.sh- Execute anybashscript, which can execute admin commands via theasadmincommand line tool -
${PATH_GF_HOME}/custom/init.asadmin- Execute asadmin commands directly
If both of the above scripts are present, they are executed in this order:
init.shinit.asadmin
However, always consider to executing any asadmin configuration commands during build, because configuring the server at container startup will prolong the startup time.
Just create a file ${PATH_GF_HOME}/custom/init.asadmin (/opt/glassfish7/custom/init.asadmin), the commands will be executed before GlassFish server starts.
Within the init.asadmin file, you can specify any asadmin command. Most of the commands require that the server is running, so you'll need to start the server first, run the configuration commands, and then stop the server.
For example, to start GlassFish, increase the maximum amount of threads, and then stop it, the init.asadmin file can contain:
start-domain
set configs.config.server-config.thread-pools.thread-pool.http-thread-pool.max-thread-pool-size=1000
stop-domain
You can provide the file by mounting its directory to the /opt/glassfish7/custom directory in the container when running the container:
docker run -v ./custom:/opt/glassfish7/custom -p 8080:8080 -ti @docker.glassfish.repository@
Just create a Bash script ${PATH_GF_HOME}/custom/init.sh (/opt/glassfish7/custom/init.sh), it will be executed before GlassFish server starts.
Within the init.sh script, you can run any asadmin command, with asadmin --interactive=false multimode COMMAND. Most of the commands require that the server is running, so you'll need to start the server first, run the configuration commands, and then stop the server. If you need to run multiple commands, we recomment running asadmin commands in a single "multimode" asadmin execution to run them faster, with commands provided either on standard input or in a separate file via the asadmin --interactive=false multimode -f option.
NOTE: If you only need to execute asadmin commands before server startup, it's easier to use the init.asadmin script to execute them directly, without a bash script.
For example, to start GlassFish, increase the maximum amount of threads, and then stop it, the init.sh script can contain:
echo "start-domain
set configs.config.server-config.thread-pools.thread-pool.http-thread-pool.max-thread-pool-size=1000
stop-domain" | asadmin --interactive=false
You can provide the script by mounting its directory to the /opt/glassfish7/custom directory in the container when running the container:
docker run -v ./custom:/opt/glassfish7/custom -p 8080:8080 -ti @docker.glassfish.repository@
Applying the configuration can be a lengthy operation. If you can configure the server during build time, it's recommended running asadmin configuration commands in a custom Docker image. This moves the configuration step to the image build time instead of runtime.
To do it, simply add RUN instructions that run asadminscript with the usual arguments. For example, to move the example configuration from theinit.sh` script above to Dockerfile:
File Dockerfile:
FROM @docker.glassfish.repository@
RUN printf "start-domain \n \
set configs.config.server-config.thread-pools.thread-pool.http-thread-pool.max-thread-pool-size=1000 \n \
stop-domain" | asadmin --interactive=false
Or you can put the asadmin commands into a separate file and run it using asadmin --interactive=false multimode -f. For example:
File commands.asadmin:
start-domain
set configs.config.server-config.thread-pools.thread-pool.http-thread-pool.max-thread-pool-size=1000
stop-domain
File Dockerfile:
FROM @docker.glassfish.repository@
COPY commands.asadmin commands.asadmin
RUN asadmin --interactive=false multimode -f commands.asadmin
Let's try something more complicated.
- To modify startup arguments for GlassFish, just add
startservto the command line and then add any arguments supported by theasadmin start-domaincommand. Thestartservscript is an alias to theasadmin start-domaincommand but starts GlassFish in a more efficient way that is more suitable in Docker container. For example, to start in debug mode with a custom domain, run:
docker run glassfish startserv --debug mydomain-
Environment variable
AS_TRACE=trueenables tracing of the GlassFish startup. It is useful when the server doesn't start without any useful logs. -
docker runwith the--userargument configures explicit user id for the container. It can be useful for K8S containers. -
docker runwith-dstarts the container as a daemon, so the shell doesn't print logs and finishes. Docker then returns the container id which you can use for further commands.
docker run -d glassfishExample of running a Docker container in background, view the logs, and then stop it (with debug enabled, trace logging, and user 1000 convenient for Kubernetes):
docker run -d -e AS_TRACE=true --user 1000 glassfish startserv --debug=true
5a11f2fe1a9dd1569974de913a181847aa22165b5015ab20b271b08a27426e72
docker logs 5a11f2fe1a9dd1569974de913a181847aa22165b5015ab20b271b08a27426e72
...
docker stop 5a11f2fe1a9dd1569974de913a181847aa22165b5015ab20b271b08a27426e72