che-server | Che Server provides an API for managing Kubernetes

I found that by adding the following above the WordPress HTACCESS directives resolved the issue:

I am able to solve it.

The problem is like I mentioned in my question. While at the time of startup each service takes lot of memory (see the logs in the question section), so there is no memory remaining for rest of the services and because of that rest of the service failed while starting with the message related to memory.

The changes I made to the docker-compse.yml file and those are:

I am able to solve the issue. Solution is to create a separate docker file to create a tomcat image and used it in docker composer file.

The problem is, even the war is copied to webapps folder of tomcat it wont deploy. See the logs for reference:

I was able to figure this out by referring to the Spring Docs on lambda functions. The problem is that they have a typo, it says "lamba" not lambda: https://docs.spring.io/spring-restdocs/docs/current/reference/html5/#working-with-asciidoctor-customizing-tables-formatting-problems.

Going off of the tabelCellContent lambda function. I found an example in the tests for StandardWriterReslover. https://www.codota.com/code/java/classes/org.springframework.restdocs.snippet.StandardWriterResolver.

The lambda function is added to the map templateContext:

In core Docker, there are two separate concepts. An image is a built version of some piece of software packaged together with its dependencies; a container is a running instance of an image. There are separate docker build and docker run commands to build images and launch containers, and you can launch multiple containers from a single image.

Docker Compose wraps these concepts. In particular, the build: block corresponds to the image-build step, and that is what invokes the Dockerfile. None of the other Compose options are available or visible inside the Dockerfile. You cannot access the container_name: or environment: variables or volumes: because those don't exist at this point in the build lifecycle; you also cannot contact other Compose services from inside the Dockerfile.

It's pretty common to have multiple containers run off the same image if they have largely the same code base but need a different top-level command. One example is a Python Django application that needs Celery background workers; you'd have the same project structure but a different command for the Celery worker.

Varnish is an excellent candidate when it comes to web acceleration. But there will be challenges.

Unfortunately, your use case cannot be satisfied with the open source version of Varnish.

The challenge you'll have is keeping track of every backend. The fact that you have thousands of images, each with their own endpoint, using a different hostname, will make your backend definitions complicated.

For every hostname, a backend should be defined, which would lead to massive amounts of backends. When starting up Varnish, each backend is tested, which could lead to a very slow startup time.

Varnish Enterprise has a module called "dynamic backends", which allows you to define backends on the fly. You can compose the hostname of a backend at runtime, and interface with other systems to determine that hostname.

This allows you the flexibility you need, and will reduce the overhead.

Here's a simplistic example of the goto module that handles dynamic backends:

Typically, you would target the Flask server rather than the Dash app in the wsgi script. That is, instead of

Fixed it. This is how to fix it: Change Apache service name. And then, while Apache is not running, click on the red cross (in the screenshot you see a green check mark but this was a red cross first) this will install Apache. Then run localhost en go to http://localhost:8080 and now its working. Two XAMPPs running at the same time.

Screenshot of chaning the Apache service name (you can go here by clicking on the Config button which you see also in the screenshot at the upper right corner):

In services you can see that there are two Apache running now from two XAMPP installations:

As Heapster is deprecated in later version(v 1.13) of kubernetes, You can expose your metrics using metrics-server also, Please check following answer for step by step instruction to setup HPA:

How to Enable KubeAPI server for HPA Autoscaling Metrics