3 ms·

But the idea is that you put the very same docker image to production. I guess most products come with an automated way to setup docker, including a decently se

But the idea is that you put the very same docker image to production. I guess most products come with an automated way to setup docker, including a decently secure setup (in this case).

derefr 9y ago
Yeah, but I'm not trying to do development of a product; I'm trying to learn the stack and/or comparatively evaluate the software for fit for a use-case. When it insists on being configured to run in "JVM-eats-all-your-RAM production mode", even though I want to operate it in "stay out of my way because I'm running you as a background service on the puny Pentium-M Macbook I develop on" mode, I get a bit miffed. And this is the same software that behaves perfectly reasonably when installed as a package directly on a Linux box; it's just when it thinks it's being used over the network because I'm running macOS and it needs to be in a Linux sandbox, that it starts acting all aggressive. At least give me a flag to let me explicitly tell the software to relax!
- jasontedor 9y ago
  I'm sorry that you're frustrated. Maybe the following will help? There is such a flag for your use case[1]. Start the node in the Docker container with discovery.type: single-node This allows the node to bind HTTP and transport protocols to non-localhost interfaces and not enforce the bootstrap checks[2][3]. The node can not form a cluster with another node, but that's okay for development use cases. It's design was intended to address the Docker development use case. I hope that helps! Disclaimer: I work at Elastic; I welcome any and all feedback [1]: https://www.elastic.co/guide/en/elasticsearch/reference/5.5/bootstrap-checks.html#_development_vs_production_mode https://www.elastic.co/guide/en/elasticsearch/reference/5.5/... [2]: https://github.com/elastic/elasticsearch/pull/23595 https://github.com/elastic/elasticsearch/pull/23595 [3]: https://github.com/elastic/elasticsearch/pull/23598 https://github.com/elastic/elasticsearch/pull/23598

But the idea is that you put the very same docker image to production. I guess most products come with an automated way to setup docker, including a decently secure setup (in this case).

derefr 9y ago

Yeah, but I'm not trying to do development of a product; I'm trying to learn the stack and/or comparatively evaluate the software for fit for a use-case. When it insists on being configured to run in "JVM-eats-all-your-RAM production mode", even though I want to operate it in "stay out of my way because I'm running you as a background service on the puny Pentium-M Macbook I develop on" mode, I get a bit miffed. And this is the same software that behaves perfectly reasonably when installed as a package directly on a Linux box; it's just when it thinks it's being used over the network because I'm running macOS and it needs to be in a Linux sandbox, that it starts acting all aggressive. At least give me a flag to let me explicitly tell the software to relax!

jasontedor 9y ago
I'm sorry that you're frustrated. Maybe the following will help? There is such a flag for your use case[1]. Start the node in the Docker container with discovery.type: single-node This allows the node to bind HTTP and transport protocols to non-localhost interfaces and not enforce the bootstrap checks[2][3]. The node can not form a cluster with another node, but that's okay for development use cases. It's design was intended to address the Docker development use case. I hope that helps! Disclaimer: I work at Elastic; I welcome any and all feedback [1]: https://www.elastic.co/guide/en/elasticsearch/reference/5.5/bootstrap-checks.html#_development_vs_production_mode https://www.elastic.co/guide/en/elasticsearch/reference/5.5/... [2]: https://github.com/elastic/elasticsearch/pull/23595 https://github.com/elastic/elasticsearch/pull/23595 [3]: https://github.com/elastic/elasticsearch/pull/23598 https://github.com/elastic/elasticsearch/pull/23598