# Seeking advice on setting up the ELK Stack

**URL:** <https://discuss.elastic.co/t/seeking-advice-on-setting-up-the-elk-stack/348968>\
**Category:** Elasticsearch\
**Created:** [December 9, 2023, 8:10pm UTC](https://discuss.elastic.co/t/seeking-advice-on-setting-up-the-elk-stack/348968 "2023-12-09T20:10:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carrier99](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@Carrier99](https://discuss.elastic.co/u/Carrier99)\
**Post date:** [December 9, 2023, 8:10pm UTC](https://discuss.elastic.co/t/seeking-advice-on-setting-up-the-elk-stack/348968/1 "2023-12-09T20:10:23Z")

</div>

Hey there.

I want to set up the ELK stack, and I'm wondering about a good way to set it up.

I'm running Proxmox so I have the options of either VMs or LXCs (was thinking of going with LXCs).

My main question is should it all just be ran in the same LXC/VM, all in separate LXCs/VMs, or maybe with some parts together and some parts separately?

Any thoughts? Sorry if this seems like a dumb question!

(For clarification, LXC refers to a Linux container.)

---

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [December 12, 2023, 12:30am UTC](https://discuss.elastic.co/t/seeking-advice-on-setting-up-the-elk-stack/348968/2 "2023-12-12T00:30:36Z")

</div>

I'm going to preface my response by stating I'm not familiar with LXC.

* * *

The answer here somewhat depends on your own objectives, but if you're looking to just spin up a stack to learn/tinker with Elastic, I'd recommend setting up a single Linux VM, install Docker (and Docker Compose) and follow one of [these guides](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html).

(Side Note: There isn't a single node Docker Compose file, but you can use the [multi-node compose file](https://github.com/elastic/elasticsearch/blob/main/docs/reference/setup/install/docker/docker-compose.yml) and just delete any/all references to `esm02` and `esm03`. There is also a simple one for [Enterprise Search setup](https://www.elastic.co/guide/en/enterprise-search/current/docker.html#docker-compose-example) that is single node as well).

The main reason I recommend going with Docker & Docker-Compose for learning/tinkering is it is probably the "least friction" method for setting up an Elastic Stack these days.

* * *

If you're more interested in setting up/learning how to operate a production grade Elastic Stack, I'd recommend again looking at using Docker for this, just spreading the Elasticsearch nodes across multiple hosts.

Depending on how "fancy" you want to get, [Elastic ECK](https://www.elastic.co/guide/en/cloud-on-k8s/current/index.html) is a pretty good way to deploy the Elastic Stack on Kubernetes.

* * *

Opinionated Note: These days in general I avoid using things like `rpm` and `deb` package installs and would definitely avoid building any sort of "custom" deployment methods. The Elastic Stack is a pretty complex beast with all the products it includes and can become a challenge to deal with when mixing in "customizations". Docker (or containers in general) I've found to provide the most "reliable/consistent" deployment method.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 9, 2024, 12:30am UTC](https://discuss.elastic.co/t/seeking-advice-on-setting-up-the-elk-stack/348968/3 "2024-01-09T00:30:39Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
