Running my ChatBot application inside Docker Liberty profile container

  • 23 May, 2017

I used the steps bellow to run my chatbot servlet application inside of a Docker container.

1 - Download WAS Liberty Docker image:

docker pull websphere-liberty

2 - Create a Docker file with the following lines

FROM websphere-liberty ADD ChatBot.war /opt/ibm/wlp/usr/servers/defaultServer/dropins/ ADD server.xml /opt/ibm/wlp/usr/servers/defaultServer/ ENV LICENSE accept

ChatBot.war is my chatbot application. To add features and configuration for your server you need to update the server.xml. Do not forget to put host=“*” on httpEndpoint or you will not access the server from your browser.

The server.xml is listed below

<!-- Enable features –> javaee-7.0 localConnector-1.0 distributedMap-1.0 webCache-1.0 <!--   –> <!-- To access this server from a remote client add a host attribute to the following element, e.g. host=“*” –> <!-- Automatically expand WAR files and EAR files –>

3 - execute docker built -t chatbot . 4 - execute docker run -d -p 80:9080 -p 443:9443 chatbot 5 - Open your browser and access your application using localhost.

Prev

Related Posts

How to Use Podman with the GitHub MCP Server: Fixing the ENOENT Error on IBM Bob

  • 17 Jun, 2026

If you are exploring the new world of the Model Context Protocol (MCP) and trying to install the GitHub MCP server on IBM Bob, there is a good chance the documentation pointed you toward Docker. But what if you use Podman as your open-source, daemonless alternative? In theory, Podman's command compatibility should make the transition seamless. In practice, AI tools or managers like Bob/VS Code can run into unexpected environment issues. In this post, we will look at how to properly configure Podman for the GitHub MCP Server and, more importantly, how to resolve the persistent command-not-found (ENOENT) error, even after setting up terminal aliases. The Initial Plan: Creating a Docker Ali

How to Use Podman with the GitHub MCP Server: Fixing the ENOENT Error on IBM BobRead More

Docker grace period ends on January 31

  • 26 Jan, 2022

I received an email yesterday from Docker. It's a reminder about the end of grace period. Hello, As a reminder you’re receiving this email because on August 31, 2021 we updated the terms(https://email.notify.docker.com/c/eJyFj0FuxCAMRU9DdkRgknSyyGKkaq5ROWAImgARIRP19iVtF91VsmTp2fb30w9DWQbP4EAEBJ6AXJQt9YaY8UN7Q3VCEDEOhFT8fazNUkKbc6hWaZRuxA4jgOhlBZkG-6U3czwI0dYOVzTotpWw7U3cGj1rnef5xqGAlh2vtP5Dvx7zr7LfiU-Q75ZfXxNFlokCxMPU4SvjQGDb0LjL1fr3NheTQ8UzBR1M9XMYq2ij7ZBgMlyKQ8Ueo-xTQr79wT0fWVOHF3BGbPD0p-tRqzC9cl1RDu2v2HbZM936AvzFbcY) applicable to the Docker products or services you use. On January 31, 2022, the grace period ends for free commercial use of Docker Desktop in larger enterprises. Companie

Docker grace period ends on January 31Read More

A rootless Pod for wordpress

  • 07 Dec, 2021

Podman Pods are very similar to Kubernetes pods in a way that they can have more than one container. Every Podman pod contains one infra container by default. This container is responsible for associating the names space with the pod and allowing podman to connect the containers to another pod. Create a Pod using Podman The first step is to create a Pod using podman: sudo podman pod create –name For our example we will create a pod with the name wp-pod sudo podman pod create -p 8080:80 --name wp-pod After creating the Pod you can see the infra container using the command: sudo podman pod ps -a --pod Note that host port 8080 has been redirected to port 80 of the pod. Pod port settin

A rootless Pod for wordpressRead More