You can run several Elasticsearch deployments on one VPS with Docker, but first decide whether you need independent standalone instances or nodes belonging to one cluster. Standalone containers isolate applications or environments; a cluster shares data and workload across nodes. The choice changes discovery settings, ports, storage, networking and failure behavior.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
Give every container its own name, host HTTP port and persistent data volume. For a cluster, use unique node names, one cluster name, private discovery and transport networking, and first-start bootstrap settings. In both designs, budget memory for every JVM, raise the VPS file-descriptor and kernel limits, pin the image version, and treat authentication, TLS and backups as part of the initial deployment.
As an Amazon Associate I earn from qualifying purchases.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallDecide what “multiple instances” means
The phrase can describe two fundamentally different topologies. Choose one before writing a Compose file.
| Decision point | Independent instances | One multi-node cluster |
|---|---|---|
| Purpose | Keep applications, teams or environments isolated. | Distribute shards and coordinate nodes as one Elasticsearch service. |
| Discovery | Each service deliberately uses discovery.type=single-node. |
Nodes use discovery.seed_hosts and a one-time cluster.initial_master_nodes bootstrap. |
| Names | Unique Compose service and container names. | Unique node.name values plus one shared cluster.name. |
| HTTP access | Different host ports, such as 9200, 9201 and 9202, while each container still listens on 9200 internally. | Publish only the node or proxy that clients need; keep node-to-node transport on the private Docker network. |
| Storage | One volume per standalone service. | One volume per node, with shard, replica and backup planning for the cluster. |
| Failure behavior | A failed container affects only its own application or environment. | Work can be redistributed only when enough eligible nodes and correctly configured discovery remain available. |
| Resource cost | Every instance adds another JVM, file descriptors and operating-system overhead. | Several JVMs plus cluster coordination make this substantially heavier on a small VPS. |
Use independent instances when isolation is the requirement
Choose this design for examples such as production and staging, or two applications that must not share indices, credentials or failure domains. The containers do not discover one another and each is its own single-node cluster. They can use separate Docker networks when isolation is useful.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Use a cluster when shared capacity or node redundancy is the requirement
A cluster is not just several copies of the standalone example. It needs shared cluster settings, seed hosts that resolve over a private network, unique node names and a controlled first-master bootstrap. Do not set discovery.type=single-node on any node intended to join this cluster.
Prepare the VPS before starting Docker
Budget memory for every Elasticsearch JVM
Each container runs another Elasticsearch JVM. Add the heap and native memory of all instances, then reserve RAM for the Linux kernel, Docker, a reverse proxy, monitoring and the rest of the application workload. Automatic JVM heap sizing assumes Elasticsearch is the only resource-intensive application on the host; that assumption is unsafe on a shared VPS.
Set an explicit Compose mem_limit for each service and size the VPS for the combined limits rather than treating them as independent numbers. Watch swap activity, container restarts and disk pressure after launch. A limit that is too low causes out-of-memory failures; limits that consume nearly all host RAM leave no room for the operating system or filesystem cache.
Apply the host limits Elasticsearch expects
- Raise the Linux open-file limit to at least 65,535. Set the host limit and, where appropriate, the Compose
ulimits.nofilevalue. - Apply Elasticsearch’s required kernel settings, including
vm.max_map_count, on the VPS host before the containers start. Use the value and persistence method required by the Elasticsearch version you have pinned. - Confirm that the limit survives a reboot and that Docker containers inherit it; changing a shell session alone is not sufficient.
Use persistent, suitable storage
Keep Elasticsearch data on persistent SSD-backed storage. A container’s writable layer is not a database backup and should not be the only place that indices exist. Mount /usr/share/elasticsearch/data from a dedicated named volume or host directory for every service or node, and maintain backups outside the container filesystem.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Choose a security boundary
Plan the access path before exposing a port. A safer VPS layout binds Elasticsearch to localhost or a private interface and lets a reverse proxy, VPN or SSH tunnel provide controlled access. If a public HTTP binding is unavoidable, require authentication, TLS and restrictive firewall rules. Keep credentials out of the Compose file when your secret-management process permits it.
Run independent standalone instances
Compose pattern with separate ports, volumes and networks
The following pattern runs production and staging as separate single-node clusters. Both containers use Elasticsearch’s internal HTTP port 9200, but the host ports and data volumes are different. The image tag is supplied through STACK_VERSION; set it to the exact release you have tested rather than using a floating latest tag.
services:
es-prod:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
container_name: es-prod
environment:
- discovery.type=single-node
- ELASTIC_PASSWORD=${PROD_PASSWORD}
- xpack.security.enabled=true
ports:
- '127.0.0.1:9200:9200'
mem_limit: ${PROD_MEM_LIMIT}
ulimits:
nofile:
soft: 65535
hard: 65535
volumes:
- es-prod-data:/usr/share/elasticsearch/data
networks:
- prod-net
es-staging:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
container_name: es-staging
environment:
- discovery.type=single-node
- ELASTIC_PASSWORD=${STAGING_PASSWORD}
- xpack.security.enabled=true
ports:
- '127.0.0.1:9201:9200'
mem_limit: ${STAGING_MEM_LIMIT}
ulimits:
nofile:
soft: 65535
hard: 65535
volumes:
- es-staging-data:/usr/share/elasticsearch/data
networks:
- staging-net
volumes:
es-prod-data:
es-staging-data:
networks:
prod-net:
staging-net:Define STACK_VERSION, both passwords and both memory-limit variables in the project’s environment management. Use long, unique secrets. Do not point two services at the same host directory or named volume: Elasticsearch data paths belong to one instance only.
What each setting does
container_nameand the service key are unique, so Docker does not try to create two containers with the same identity.discovery.type=single-nodeprevents this service from waiting for peers. It is correct here because each service is intentionally its own cluster.- The host mappings
9200:9200and9201:9200distinguish client endpoints without changing Elasticsearch’s internal port. - Binding to
127.0.0.1keeps the ports off the public interface. Use a reverse proxy, VPN or tunnel for remote clients. - The two named volumes preserve data independently through container recreation.
- The explicit memory and file-descriptor settings make resource assumptions visible instead of relying on Docker or host defaults.
Start and verify the standalone services
- Create a project directory and a Compose file, then create the environment values for the pinned image tag, passwords and memory limits.
- Run
docker compose configlocally to catch YAML and variable-interpolation errors. Treat its rendered output as sensitive because it can contain resolved settings. - Start the services with
docker compose up -d. - Check container state with
docker compose ps. Both services should show as running. - Inspect startup failures with
docker compose logs --tail=200 es-prodor the equivalent staging service. - Query each endpoint with its own credentials, for example
curl -u elastic:$PROD_PASSWORD http://127.0.0.1:9200. When HTTP TLS is enabled, usehttpsand the configured certificate authority instead. - Restart one service with
docker compose restart es-prod, query it again and confirm that its indices remain. Repeat for staging; a restart test validates that the volume, not the container layer, holds the data.
Build one multi-node cluster
Compose pattern for three nodes
Use one shared Docker network and a unique data volume for every node. The service names es01, es02 and es03 become resolvable discovery addresses on that network.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
services:
es01:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
container_name: es01
environment:
- node.name=es01
- cluster.name=${CLUSTER_NAME}
- discovery.seed_hosts=es02,es03
- cluster.initial_master_nodes=es01,es02,es03
- ELASTIC_PASSWORD=${ELASTIC_PASSWORD}
- xpack.security.enabled=true
ports:
- '127.0.0.1:9200:9200'
mem_limit: ${ES_MEM_LIMIT}
ulimits:
nofile:
soft: 65535
hard: 65535
volumes:
- esdata01:/usr/share/elasticsearch/data
networks:
- es-cluster
es02:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
container_name: es02
environment:
- node.name=es02
- cluster.name=${CLUSTER_NAME}
- discovery.seed_hosts=es01,es03
- cluster.initial_master_nodes=es01,es02,es03
- xpack.security.enabled=true
mem_limit: ${ES_MEM_LIMIT}
ulimits:
nofile:
soft: 65535
hard: 65535
volumes:
- esdata02:/usr/share/elasticsearch/data
networks:
- es-cluster
es03:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
container_name: es03
environment:
- node.name=es03
- cluster.name=${CLUSTER_NAME}
- discovery.seed_hosts=es01,es02
- cluster.initial_master_nodes=es01,es02,es03
- xpack.security.enabled=true
mem_limit: ${ES_MEM_LIMIT}
ulimits:
nofile:
soft: 65535
hard: 65535
volumes:
- esdata03:/usr/share/elasticsearch/data
networks:
- es-cluster
volumes:
esdata01:
esdata02:
esdata03:
networks:
es-cluster:This is a topology pattern, not a complete production certificate bundle. Add the HTTP-TLS and transport-TLS settings, certificate mounts and certificate-authority handling required by your pinned Elasticsearch release before allowing client or inter-node traffic outside the private network.
Understand discovery and first bootstrap
cluster.name must match on every node. Each node.name must be unique. discovery.seed_hosts lists peer service names used to find the initial cluster; those names work because all nodes share the es-cluster network.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemscluster.initial_master_nodes is for the first cluster bootstrap only. Start the intended initial master-eligible nodes together, verify that one cluster forms, and remove the initial-bootstrap setting from the configuration used for later restarts. Never reuse the bootstrap list to create a second cluster from existing data.
Do not add discovery.type=single-node to any service in this topology. That setting tells Elasticsearch to operate alone and conflicts with the discovery process required for a cluster.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Publish only the client endpoint you need
The sample publishes HTTP for es01 on localhost and leaves the other nodes un-published. A reverse proxy can present one stable endpoint, or you can publish additional HTTP ports on localhost if an operator needs direct access. Keep the transport interface used for node communication on the Docker network; it should not be opened to the public internet.
Start and verify the cluster
- Set one pinned
STACK_VERSION, one cluster name and the secrets used by your security configuration. - Prepare certificates, certificate authorities and secure mounts before enabling HTTP or transport TLS.
- Run
docker compose config, checking that every node has a distinct name and volume. - Start with
docker compose up -d, then inspectdocker compose psand each node’s logs. - Query the published endpoint using authentication and HTTPS when configured. Check
/_cluster/healthand confirm that all expected nodes have joined. - After the initial cluster is formed, remove the first-bootstrap setting from the repeatable restart configuration, while retaining the persistent volumes and normal discovery seed hosts.
- Stop and start one node at a time during a controlled test. Verify that the cluster reports the expected node count and that indices remain available according to their replica configuration.
Networking, security and exposure
Separate client traffic from transport traffic
Compose’s private network provides name resolution and an internal path for cluster communication. Publish HTTP only where a client, reverse proxy or administrator actually needs it. Publishing every node and the transport port creates unnecessary attack surface and can allow untrusted hosts to attempt cluster communication.
For independent instances, separate networks prevent accidental service-to-service access. For a cluster, all nodes must share one private network so discovery and transport connections can resolve each other.
Enable authentication and TLS deliberately
The official multi-node Compose approach enables xpack.security.enabled, HTTP TLS and transport TLS, and supplies certificate authorities. Follow that model rather than treating security as a later cleanup task. Replace example passwords and certificates with values managed for your environment, and do not commit secrets or private keys to a public repository.
When TLS is enabled, clients need the correct scheme, credentials and certificate authority. A plain HTTP probe can look like a connection failure even when Elasticsearch is healthy if the endpoint requires HTTPS.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Firewall the host
Allow only the reverse proxy, VPN range or known administration addresses to reach the published interface. If the service is bound to localhost, the firewall does not need to expose Elasticsearch directly. Keep the VPS provider’s firewall and the host firewall aligned with the same access policy.
Persistence, backups and lifecycle operations
Prove that data survives recreation
Removing a container is safe only when its data path is an external named volume or host directory. Before accepting production traffic, create a test index, record its contents, recreate the container and query the index again. Perform the same test for every standalone service and every cluster node.
Back up outside Docker
Maintain backups outside the container filesystem and outside the single VPS failure domain when possible. Document where backups are stored, how credentials are protected and how an index or cluster would be restored. A backup that has never been restored is an assumption, not a recovery plan.
Pin and change versions intentionally
Use a specific Elastic image tag in STACK_VERSION. Review release compatibility and take a verified backup before changing the tag. Pull and recreate the intended service through Compose while retaining its data volume; do not silently switch all instances to a floating tag at once. On a cluster, plan the order of node changes and monitor cluster health between each operation.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
Troubleshoot the failures that occur most often
| Symptom | Likely cause | What to check or change |
|---|---|---|
| Compose reports that a port is already allocated. | Another service already owns the host port, or two instances use the same mapping. | Run docker compose ps and inspect the host listener. Give each standalone service a different host port, or bind only the intended cluster endpoint. |
| A container exits during startup with a bootstrap or kernel error. | The VPS kernel or file-descriptor limits are below Elasticsearch’s requirements. | Check the host’s vm.max_map_count and open-file limits, then verify the container’s effective nofile value. Apply persistent host settings and recreate the container. |
| Cluster nodes never join. | Names do not resolve, the seed list is wrong, the nodes use different cluster names, or transport traffic is blocked. | Confirm that all nodes share the intended Docker network, that es01, es02 and es03 resolve inside it, and that every node.name, cluster.name and seed-host entry is correct. |
| Every restart appears to lose indices. | The data path was left in the container layer, the volume was not mounted, or a different volume name was used. | Inspect docker inspect mounts and the Compose volume declarations. Stop using the container filesystem and restore from the appropriate backup if data was already lost. |
| The VPS swaps heavily or containers are killed. | The sum of JVM and container limits leaves too little RAM for the host and other services. | Reduce the number of instances, lower appropriately sized heaps or move to a larger VPS. Do not solve sustained memory pressure by simply adding more containers. |
| Authentication succeeds over HTTP but fails after TLS is enabled. | The client is using the wrong scheme or does not trust the configured certificate authority. | Use the HTTPS endpoint, supply the correct CA and credentials, and inspect the Elasticsearch and proxy logs for certificate or hostname errors. |
| A node with existing data tries to form a new cluster. | First-bootstrap settings were left in a repeatable configuration or the persistent data was replaced. | Stop the node, verify the intended data volume and cluster identity, remove the initial bootstrap setting for normal restarts, and follow the documented recovery procedure rather than deleting data casually. |
Pre-exposure checklist
- Every container or node has a unique name and its own data volume.
- Standalone services have distinct host HTTP ports; cluster transport remains private.
- The image tag is pinned and recorded for rollback.
- Memory limits account for all JVMs, Docker, the operating system and the application workload.
- The host has at least 65,535 open-file descriptors available to Elasticsearch and the required kernel settings are persistent.
- Authentication is enabled, TLS certificates and authorities are managed securely, and passwords are not committed to source control.
- Elasticsearch ports are bound to localhost or a private interface unless a documented firewall and TLS policy requires public access.
- Backups exist outside the container filesystem, and a restore test has been performed.
- A restart test confirms that indices survive container recreation.
- For a cluster, seed hosts resolve, initial bootstrap is used only once, all expected nodes appear in cluster health, and no node uses
discovery.type=single-node.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
