iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
Running several Elasticsearch containers on one VPS can mean two very different designs: independent standalone instances for separate applications or environments, or several nodes that form one Elasticsearch cluster. Choose the design first. Standalone instances need separate names, host ports and data volumes; cluster nodes need shared discovery, unique node names and coordinated bootstrap settings.
The procedures below use Docker Compose, persistent storage and private networking. They also account for the constraints that matter on a VPS: every container starts another JVM, Elasticsearch needs high file-descriptor limits, and security, TLS, backups and version pinning must be planned before the first start.
Windows 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 reinstallCrashes, 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 minuteDecide whether you need separate instances or one cluster
An independent instance is its own Elasticsearch cluster, even when several such containers run on the same VPS. This is appropriate when production and staging must never share indices, when different applications require administrative isolation, or when each environment should be stopped and upgraded independently.
A multi-node cluster is one logical Elasticsearch deployment. Nodes share a cluster name, discover one another and distribute shards. Use it for node redundancy and shard distribution, not merely to run two unrelated applications. A cluster does not automatically make a small VPS highly available: it needs enough eligible nodes, separate failure domains where possible and correctly configured discovery.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
| Decision point | Independent instances | One multi-node cluster |
|---|---|---|
| Purpose | Isolation between applications, tenants or environments | One dataset distributed across cooperating nodes |
| Discovery | discovery.type=single-node for each deliberately standalone service |
Seed hosts plus first-cluster bootstrap settings; never discovery.type=single-node |
| HTTP exposure | Different host ports such as 9200, 9201 and 9202 | Publish only the HTTP endpoint clients need; keep transport traffic private |
| Storage | One volume or host directory per instance | One volume per node, with shard and backup planning |
| Failure behavior | A failed container affects only its application | The cluster can redistribute work only when sufficient eligible nodes remain |
| Resource cost | Each container consumes memory, file descriptors and disk | Several JVMs plus cluster overhead; substantially heavier on a small VPS |
Prepare the VPS before creating containers
Size memory for every JVM and the host
Count every Elasticsearch container, then reserve memory for its JVM, filesystem cache, Docker, the operating system, a reverse proxy and your application workload. Automatic JVM heap sizing assumes Elasticsearch is the only resource-intensive application on the host; that assumption is rarely true on a shared VPS. Set explicit Compose memory limits and monitor both RAM and swap instead of allowing one container to consume the machine.
Do not infer a safe node count from CPU cores alone. A configuration that starts successfully can still thrash when indexing, searching and segment merges occur together. Leave operating-system headroom and keep enough disk space for data, translogs, temporary files and snapshots.
Raise Linux limits and apply kernel requirements
Elastic system guidance requires at least 65,535 open file descriptors. Check the current limit on the VPS and raise it for the Docker service and the host user according to your distribution’s service configuration. Also apply Elasticsearch’s required kernel settings, including vm.max_map_count, on the VPS host before startup; container-level changes alone are not a substitute for the host setting.
ulimit -n
sysctl vm.max_map_countAfter changing limits, restart the relevant service or VPS and verify the values again. A container that exits during bootstrap with file, virtual-memory or bootstrap-check errors is usually reporting a host configuration problem rather than a Compose syntax error.
Use persistent, separate storage
Mount persistent SSD-backed storage at /usr/share/elasticsearch/data. Give every instance or node its own named volume or host directory. Never mount the same data directory into two running containers: Elasticsearch data files belong to one node and concurrent access can corrupt the store.
Keep backups outside the container filesystem and test restoration. A Docker volume is persistence across container replacement, not a backup. Plan disk monitoring before indexing begins.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Pin the image and protect secrets
Use a specific Elastic image tag through STACK_VERSION rather than an unpinned latest tag. Put passwords and other secrets in a protected environment file or secret mechanism, restrict its permissions, and do not commit it to source control. Upgrades should be deliberate and compatible with your existing data and cluster version.
Run independent Elasticsearch instances
Compose pattern
The following pattern creates production and staging as separate standalone clusters. Both containers listen on Elasticsearch’s internal port 9200, while the VPS maps them to different loopback ports. Add a third service by repeating the same pattern with a new service name, password, port and volume.
services:
es-prod:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
environment:
- discovery.type=single-node
- ELASTIC_PASSWORD=${PROD_PASSWORD}
- xpack.security.enabled=true
mem_limit: 2g
ports:
- '127.0.0.1:9200:9200'
volumes:
- es-prod-data:/usr/share/elasticsearch/data
es-staging:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
environment:
- discovery.type=single-node
- ELASTIC_PASSWORD=${STAGING_PASSWORD}
- xpack.security.enabled=true
mem_limit: 2g
ports:
- '127.0.0.1:9201:9200'
volumes:
- es-staging-data:/usr/share/elasticsearch/data
volumes:
es-prod-data:
es-staging-data:The 2g limits are illustrative, not a universal heap recommendation; choose limits after sizing the complete VPS. The important invariants are unique service or container names, unique host-side ports and a unique data volume for each service. Binding to 127.0.0.1 keeps the HTTP APIs off the public interface so a reverse proxy, VPN or SSH tunnel can provide controlled access.
Keep each standalone service isolated
Compose creates a project network automatically. For stronger separation, place services in distinct user-defined networks and connect only the application that should reach each instance. Do not reuse a data directory when cloning a service. Copy the Compose definition, change the service name, credentials, port and volume, then start the new service with its own data path.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Deploy and verify the instances
-
Create a project directory and a protected
.envfile containing a pinnedSTACK_VERSION,PROD_PASSWORDandSTAGING_PASSWORD. -
Save the Compose file, then run
docker compose config. This expands variables and catches YAML or interpolation errors before containers start. -
Start the services with
docker compose up -d. -
Check state with
docker compose ps. If a service is unhealthy or repeatedly exits, inspectdocker compose logs --tail=200 es-prodor the corresponding staging service. -
Query each endpoint through its loopback port using the configured credentials and HTTPS when enabled. Confirm that production and staging return different cluster identities and that each can create and read an index.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Restart one service with
docker compose restart es-prod, then verify its index remains. Persistence across this test demonstrates that the volume is mounted; it does not replace a backup test.
Build one multi-node cluster
Cluster-specific settings
Every node needs a unique node.name. All nodes use the same cluster.name and list the other nodes, by Compose service name, in discovery.seed_hosts. Set cluster.initial_master_nodes only for the first bootstrap of a brand-new cluster, listing the node names that are eligible to form the initial master quorum. Once the cluster has formed and its data is persistent, remove that bootstrap setting from the normal restart configuration; it is not a recovery switch for an existing cluster.
Never combine this design with discovery.type=single-node. That option deliberately disables normal multi-node discovery and would prevent the intended cluster formation.
Compose skeleton
services:
es01:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
environment:
- node.name=es01
- cluster.name=app-search
- discovery.seed_hosts=es02,es03
- cluster.initial_master_nodes=es01,es02,es03
- ELASTIC_PASSWORD=${ELASTIC_PASSWORD}
- xpack.security.enabled=true
- xpack.security.http.ssl.enabled=true
- xpack.security.transport.ssl.enabled=true
mem_limit: 2g
volumes:
- esdata01:/usr/share/elasticsearch/data
networks:
- elastic-internal
es02:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
environment:
- node.name=es02
- cluster.name=app-search
- discovery.seed_hosts=es01,es03
- cluster.initial_master_nodes=es01,es02,es03
- ELASTIC_PASSWORD=${ELASTIC_PASSWORD}
- xpack.security.enabled=true
- xpack.security.http.ssl.enabled=true
- xpack.security.transport.ssl.enabled=true
mem_limit: 2g
volumes:
- esdata02:/usr/share/elasticsearch/data
networks:
- elastic-internal
es03:
image: docker.elastic.co/elasticsearch/elasticsearch:${STACK_VERSION}
environment:
- node.name=es03
- cluster.name=app-search
- discovery.seed_hosts=es01,es02
- cluster.initial_master_nodes=es01,es02,es03
- ELASTIC_PASSWORD=${ELASTIC_PASSWORD}
- xpack.security.enabled=true
- xpack.security.http.ssl.enabled=true
- xpack.security.transport.ssl.enabled=true
mem_limit: 2g
volumes:
- esdata03:/usr/share/elasticsearch/data
networks:
- elastic-internal
volumes:
esdata01:
esdata02:
esdata03:
networks:
elastic-internal:This is a structural example based on Elastic’s official Compose pattern. A production deployment also needs the certificate-authority and certificate mounts required by the enabled HTTP and transport TLS settings. Generate and store those certificates securely, use the same trusted CA for cluster transport, and replace example credentials with secrets managed outside the Compose file. Do not publish the transport port to the Internet; nodes can communicate over the private Compose network.
Recommended Free Tools
Expose only what clients require
Client applications can reach an HTTP endpoint through a private reverse-proxy network, VPN or an explicitly restricted host binding. Publish a host HTTP port only when a client or proxy needs it. Inter-node transport should remain on elastic-internal or another private interface, with firewall rules allowing only the cluster members.
Bootstrap without creating a second cluster
-
Confirm that all three service names resolve on the same private Docker network and that each node has its own empty persistent volume.
Rank #3
Sale
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black | LED mouse pad with 14 lighting modes, covers keyboard & mouse, anti-slip rubber base, waterproof surface, USB powered- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
-
Run
docker compose config, checking that the image tag, node names, seed hosts, TLS paths and memory limits are identical where they should be. -
Start the complete set with
docker compose up -drather than repeatedly starting isolated nodes with single-node discovery.Free tools Windows power users keep installed
One-click scans. No signup required.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Read
docker compose logs --tail=200 es01,es02andes03for certificate, bootstrap or discovery errors. -
Authenticate to one HTTP endpoint and query
_cluster/health. Confirm that the expected number of nodes joined before creating production indices. -
After the initial cluster is established, remove the initial bootstrap setting from the ordinary configuration and keep the persistent volumes. Do not delete volumes to solve a transient discovery problem; that destroys the node’s cluster metadata.
Validate operation after deployment
Check identity and membership
For independent instances, query each mapped HTTP port and verify that the returned cluster name and index list match the intended environment. For a shared cluster, query _cluster/health and confirm the node count, status and allocation state. A green status is useful but does not replace checking that every expected node is present.
Test persistence and controlled failure
Create a non-critical test index, restart one container and verify that the index remains. In a cluster, stop one node only during a maintenance window and observe whether the remaining eligible nodes maintain service and recover shards. This test reveals whether the VPS has real redundancy or merely several processes on one failure domain.
Monitor the host, not just Elasticsearch
-
Track RAM, swap activity and container memory against each Compose limit.
-
Watch disk capacity and inode usage for every data volume.
DriversCrashes, No Sound, or Screen Glitches?PerformanceWindows Errors? Fix Them Before They SpreadDriversOutdated Drivers Are Slowing You DownSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Review logs for bootstrap checks, rejected writes, circuit breakers, discovery failures and TLS errors.
Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
-
Alert on a node leaving the cluster, unassigned shards or a failed snapshot.
-
Keep firewall rules and reverse-proxy access logs under review when HTTP access is exposed.
Security requirements for a VPS
Elastic’s multi-node Compose example enables authentication, HTTP TLS and transport TLS. Follow that security model for any deployment reachable beyond a trusted private network. Keep Elasticsearch ports private wherever possible, expose a reverse proxy or VPN instead, and restrict firewall rules to known client addresses.
If a public HTTP binding is unavoidable, require authentication and TLS, use restrictive firewall rules and avoid default or shared credentials. Transport TLS is separate from HTTP TLS: clients need a trusted HTTPS certificate, while nodes need certificates that authenticate private cluster communication. Store certificate authorities, private keys and passwords with permissions that prevent ordinary application users from reading them.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common failures and precise fixes
Both containers try to use the same port
Only host-side ports must differ for independent instances. Keep the container side at 9200 and map it to 9200, 9201 or another unused loopback port. If Docker reports an address already in use, change the number before restarting.
A node exits with a bootstrap-check or file-limit error
Recheck the VPS file-descriptor limit and required kernel settings, then restart Docker and the container. The minimum open-file guidance is 65,535. Increasing a Compose memory limit will not fix a kernel or descriptor failure.
Cluster nodes cannot discover one another
Ensure all services share the same private network, use resolvable Compose service names in discovery.seed_hosts, and have matching cluster names. Check that host firewalls are not blocking private transport traffic. Remove discovery.type=single-node from every cluster node.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe cluster forms twice or refuses to bootstrap
Do not change node names or reuse a persistent volume while troubleshooting. Verify that the initial master list exactly matches the intended first bootstrap and that it is removed from the normal post-bootstrap configuration. If data was deliberately discarded, create genuinely empty volumes and perform a new bootstrap; otherwise preserve the existing cluster metadata.
HTTP requests fail after enabling TLS
Use HTTPS, supply the correct credentials and trust the configured certificate authority. Confirm that the certificate and key are mounted at the paths referenced by the container configuration. A plain HTTP request to a TLS-only endpoint is expected to fail.
Indexes disappear after a container replacement
Inspect docker inspect or the Compose volume declaration and verify that /usr/share/elasticsearch/data maps to the intended persistent volume. Recreating a container is safe only when its data volume remains attached. Recover missing data from a tested snapshot rather than copying live files between nodes.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Backups, upgrades and ongoing operations
Snapshot repositories are the reliable recovery mechanism for indices and cluster state. Keep snapshots outside the VPS or on storage that survives loss of the machine, and periodically perform a restore test. Do not treat a second container, a second volume on the same disk or a stopped container as an independent backup.
Pin the Elastic image version and schedule upgrades. Read the compatibility requirements for your current data and cluster version before changing STACK_VERSION. Upgrade cluster nodes in a controlled sequence, watch health and shard allocation after each change, and retain the previous image tag until the deployment is confirmed stable.
For independent instances, upgrade one environment at a time and verify its endpoint and indices before touching the next. For a cluster, preserve node names and volumes, maintain quorum, and never delete all node data as a shortcut for an upgrade problem.
Deployment checklist
-
Architecture chosen: independent instances for isolation, or one cluster for shared data and node coordination.
-
Every service has a unique name, image tag, host port where needed and persistent data volume.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Cluster nodes have unique node names, one cluster name, valid seed hosts and a controlled first bootstrap.
-
No cluster node uses
discovery.type=single-node. -
Transport traffic stays on a private Docker network or private interface.
-
HTTP exposure is limited to the clients, reverse proxy or VPN that require it.
-
Memory limits account for all JVMs and leave headroom for the VPS host and applications.
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 problemsSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Open files are set to at least 65,535 and required kernel settings are applied on the host.
-
Authentication, TLS, firewall rules, secret storage and certificate rotation are defined before production traffic.
-
Backups exist outside the containers and a restore has been tested.
-
docker compose config, startup logs, endpoint checks and restart tests all pass.Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Quick Recap
SaleBestseller No. 1SaleBestseller No. 4
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.
