The conventional way for creating Docker images is to use a Dockerfile, which serves as a specialized blueprint for automation by specifying required commands in a text file. This file is then interpreted and processed by the Docker daemon, which generates a new template based on the instructions. By eliminating the need to manually perform each operation, this method streamlined the process.<\/p>\n We will detail the particular procedures required in generating a custom image of the WildFly server on our platform, resulting in a fully operating Dockerized version that is ready for use within the platform.<\/p>\n Let’s proceed with the following operations, detailing each step:<\/p>\n First, create a new empty text file in which we will explain all of the essential operations. Then, continue with the instructions below.<\/p>\n Step 1.<\/strong> First, we need to specify the base template for our image building. We will use the jelasticdocker\/jelastic-centos7-base<\/strong> template, which comes pre-configured with the CentOS 7 operating system. To do this in the Dockerfile, use the FROM<\/strong> instruction as follows:<\/p>\n Step 2.<\/strong> Following that, you can give generic image information, such as metadata or internal variables, which will be required for future settings. Refer to the example below to correctly set these values:<\/p>\n where<\/p>\n Step 3.<\/strong> You are now ready to specify the appropriate configurations via shell commands. Use the ‘RUN<\/strong>‘ operator to effectively run these commands.<\/p>\n First, install the Java Development Kit (particularly, OpenJDK version 8) and the tar archiver, which will be needed to decompress downloaded files.<\/p>\n Following this command, make sure the installed packages are up to date.<\/p>\n Step 4.<\/strong> Next, specify additional procedures to download and extract the WildFly source code from the official website to the \/opt folder.<\/p>\n Step 5.<\/strong>\u00a0Create a symlink to shorten the path to the main WildFly directory, making it more accessible and navigable.<\/p>\n Step 6.<\/strong> Now, let’s create the primary configuration file for our WildFly server and add all of the relevant settings to it.<\/p>\n Step 7.<\/strong> CentOS 7 defaults to the Systemd initiation script; however, the WildFly server requires the more classic SystemV Init script.\u00a0To avoid the Systemd redirect, you must copy the default initscript to the \/etc\/init.d folder and configure it accordingly.<\/p>\n Step 8.<\/strong> Next, we’ll set up WildFly to run on container startup by creating the appropriate system user and setting file ownership accordingly.<\/p>\n Step 9.<\/strong> In addition, we will enter the user credentials defined in the first instruction step for accessing the server’s admin panel.<\/p>\n Step 10.<\/strong> We can now adjust the URL to the admin panel on the default index.html page by specifying the proper redirect. This ensures that the admin panel may be accessed properly, especially if our image is deployed to a container without an external IP address, via port 4949 and an HTTP connection.<\/p>\n Step 11.<\/strong> Add the English locale settings<\/a> to the container.<\/p>\n Step 12.<\/strong> Another step is to configure our Docker image to listen on the specified ports during runtime. This can be achieved using the ‘EXPOSE’ command.<\/p>\n Step 13.<\/strong> Finally, specify ‘ENTRYPOINT’ to define the container’s executable. In this scenario, we’ll specify the bash shell.<\/p>\n That is it! Remember to save all of the required settings to complete the dockerfile and make it ready for use.<\/p>\n Once you’ve created the required dockerfile, you can build your WildFly image and push it to the repository.<\/p>\n To proceed, follow these steps:<\/p>\n Step 1.<\/strong> Execute the `docker build` command with the necessary parameters to create a new image locally.<\/p>\n Here are the details:<\/strong><\/p>\n Next steps:<\/p>\n Step 2.<\/strong> After running the ‘docker build’ command, you should see a build success message with the ID of your new image. To ensure that it is available on your workstation, you can obtain a list of all local photos with:<\/p>\n Step 3.<\/strong> Finally, upload your image to a registry using the proper command.<\/p>\n For this step, specify the `{image_name}` identically to the one used during the image-building process in the first step.<\/p>\n By additionally authenticating your account ownership by entering the correct username password and email you can complete the procedure.<\/p>\n Once your image has been successfully stored in the repository, it will be available for use on the platform and may be added to an environment using the specific Docker board embedded into the topology wizard<\/a> dashboard.<\/p>\n To proceed, select the “New Environment” button at the top of the dashboard, then navigate to the Docker tab under the environment wizard, and finally click the “Select Image” button.<\/p>\n 1. In this section, you have two options:<\/p>\n Let us focus on the second alternative. Once inside, navigate to the required environment layer on the left (in this case, “App. Servers”) and click the “Add New Image<\/strong>” button.<\/p>\n In the opened “Add New Image<\/strong>” frame, enter your image identifier in the “Name” field following this format:<\/p>\n If you are using a private repository, make sure to provide the appropriate Username and Password credentials.<\/p>\n We’re utilizing the public Docker Hub repository, which is part of the main Registry Hub, so only the short repository name is required. When you are ready, click the “Add”<\/strong> button.<\/p>\n Once added, your image will appear on the list. From here, you may add it to the topology with a single click. Furthermore, this template will be preserved and placed here for future use, making it easier to access during subsequent container selections (unless manually removed from the Custom list).<\/p>\n Complete the remaining configurations<\/a> based on your requirements (see the attached guide for more information on available options) and finish the environment creation.<\/p>\n Once your environment with the appropriate image shows on the dashboard, click the “Open in Browser<\/strong>” option connected with it.<\/p>\n![\"Dockerfile](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/07\/01-building-wildfly-docker-image-new.jpg\" "\\"Dockerfile")
<\/a><\/p>\n\n
Composing Dockerfile<\/h2>\n
\r\nFROM jelasticdocker\/jelastic-centos7-base:latest<\/code><\/pre>\n\r\nLABEL maintainer=\"Accuweb\"\r\nENV WILDFLY_VERSION 13.0.0.Final\r\nENV ADMIN_USER jelastic\r\nENV ADMIN_PASSWORD jelastic<\/code><\/pre>\n\n
\r\nRUN yum -y install java-1.8.0-openjdk-devel tar && yum -y update;<\/code><\/pre>\n\r\nRUN cd \/opt && curl -O https:\/\/download.jboss.org\/wildfly\/${WILDFLY_VERSION}\/wildfly-${WILDFLY_VERSION}.tar.gz \\\r\n&& $(which tar) xf wildfly-${WILDFLY_VERSION}.tar.gz \\\r\n&& rm wildfly-${WILDFLY_VERSION}.tar.gz<\/code><\/pre>\n\r\nRUN ln -s \/opt\/wildfly-$WILDFLY_VERSION \/opt\/wildfly<\/code><\/pre>\n\r\nRUN echo -en \"JAVA_HOME=\\\"\/usr\/lib\/jvm\/java\\\"\"'\\n'\\\r\n\"JBOSS_HOME=\\\"\/opt\/wildfly\\\"\"'\\n'\\\r\n\"JBOSS_USER=wildfly\"'\\n'\\\r\n\"JBOSS_MODE=standalone\"'\\n'\\\r\n\"JBOSS_CONFIG=standalone.xml\"'\\n'\\\r\n\"STARTUP_WAIT=60\"'\\n'\\\r\n\"SHUTDOWN_WAIT=60\"'\\n'\\\r\n\"JBOSS_CONSOLE_LOG=\\\"\/var\/log\/wildfly\/console.log\\\"\"'\\n'\\\r\n\"JBOSS_OPTS=\\\"-b 0.0.0.0 -bmanagement=0.0.0.0 -Djboss.management.http.port=4949 -Djboss.management.https.port=4848\\\"\" >> \/etc\/default\/wildfly<\/code><\/pre>\n\r\nRUN wget https:\/\/raw.githubusercontent.com\/wildfly\/wildfly-core\/master\/core-feature-pack\/src\/main\/resources\/content\/docs\/contrib\/scripts\/init.d\/wildfly-init-redhat.sh -O \/etc\/rc.d\/init.d\/wildfly;\r\nsed -i \"\/# Source function library\/a\\SYSTEMCTL_SKIP_REDIRECT=1\" \/etc\/init.d\/wildfly; chmod +x \/etc\/init.d\/wildfly;<\/code><\/pre>\n\r\nRUN chkconfig --add wildfly; chkconfig wildfly on; mkdir -p \/var\/log\/wildfly; adduser wildfly;\r\nchown -R wildfly:wildfly \/opt\/wildfly-$WILDFLY_VERSION \/opt\/wildfly \/var\/log\/wildfly;<\/code><\/pre>\n\r\nRUN \/opt\/wildfly\/bin\/add-user.sh --user $ADMIN_USER --password $ADMIN_PASSWORD --silent --enable<\/code><\/pre>\n\r\nRUN sed -i \"s\/<a href=\\\"\\\/console\\\">\/<a href=\\\"\\\/console\\\" onclick=\\\"javascript:event.target.port=4949;event.target.protocol=\\'http:\\';\\\">\/\" \/opt\/wildfly\/welcome-content\/index.html<\/code><\/pre>\n\r\nRUN localedef -i en_US -f UTF-8 en_US.UTF-8<\/code><\/pre>\n\r\nEXPOSE 22 80 443 8080 8743 9990 9993 8009 4848 4949<\/code><\/pre>\n\r\nENTRYPOINT [\"\/bin\/bash\"]<\/code><\/pre>\nAdding Image to Repository<\/h2>\n
\r\nsudo docker build -t {image_name} {dockerfile_location}<\/code><\/pre>\n\n
\r\nsudo docker images<\/code><\/pre>\n\r\nsudo docker push {image_name}<\/code><\/pre>\nDeploying Image at Platform<\/h2>\n
\n
![\"Search](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Search-Docker-hub-repository.png\" "\\"Search")
<\/a><\/p>\n\r\n{registry_hostname} (can be skipped for official Hub Registry) \/ {account} \/ {image_name}<\/code><\/pre>\n![\"Add](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Add-new-image.png\" "\\"Add")
<\/a><\/p>\n![\"Docker](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Docker-repository.png\" "\\"Docker")
<\/a><\/p>\n
![\"Environment](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Environment-created.png\" "\\"Environment")
<\/a><\/p>\n![\"WildFly](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/WildFly-dashboard.png\" "\\"WildFly")
<\/a><\/p>\n