I am trying to deploy a docker-compose.yaml on a public cloud VM. There is no other file I would like to deploy
My file that contains 3 images to build the container (see code below): Kafka Broker, Zookeeper and Python-Producer (which basically just produces random numbers periodically and writes to a Kafka Topic; and this image is deployed publicly).
I have followed 2 comprehensive tutorials on how to deploy a container on VM using GCP & AWS EC2 meticulously. But I am getting the following errors
On AWS EC2 on Linux → I am unable to install docker-compose engine
On GCP VM on Ubuntu → I am able to run docker-compose up command but it throws an error stating the broker cannot be started
Thank you, I did not realize that docker-compose had been deprecated.
And now I am finally able to use the docker compose command to spin up containers using my YAML file.
I edited the yaml file to remove the python image and now it consists of only the zookeeper and kafka broker services. However containers keep exiting for kafka broker.
The zookeeper does not exit and runs smoothly. I also changed the docker compose yaml file and edited the PLAINTEXT_HOST to :9092
The log for the container looks like -
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000c0000000, 1073741824, 0) failed; error=‘Not enough space’ (errno=12)
There is insufficient memory for the Java Runtime Environment to continue.
Native memory allocation (mmap) failed to map 1073741824 bytes for committing reserved memory.
An error report file with more information is saved as:
Is this related to the EBS volume attached to the instance ??
(I am using a free tier EC2 instance with 1 GB EBS volume)