Sign inSign up

fuzzybunny/elastic

By fuzzybunny

•Updated over 9 years ago

Elasticsearch Indexing Component

Image
2

1.3K

fuzzybunny/elastic repository overview

⁠Status

  • Deprecated: Now part of the 3.0 baseline

⁠Latest Update: 3 May 17

  • Abandoned custom deployment and moved to Portainer based infrastructure.. for trial
    • Removed dependencies on custom scripts
    • Added default configs inside image
    • Created Portainer instructions

⁠Instructions

  • Intended for deployment using Portainer
  • If you don't know what you're doing with Portiner, follow the sections marker Portainer: .. below
  • .. or else the configuration section should have the needed information

⁠Configuration

⁠Host System Config

[ NOTE ] To be done on your host system

  • For elastic search to run properly you must adjust the maximum virtual memory areas a process may have mapped. Adjust this value as follows sysctl -w vm.max_map_count=262144

    [ WARN ] This is not persistent on system reboot.. Edit /etc/sysctl.conf to make it persistent

⁠Port Mappings
  • host 9200 -> container 9200
  • host 9300 -> container 9300
⁠Environment Variables
  • `ES_JAVA_OPTS = -Xmsg -Xmxg

    is the amount of RAM in GB that elastic search will consume. 24 is a good number, over 30ish negatively effect performance

⁠Volume Mappings
  • If you don't want to use the default configuration file, you can map a custom one to /usr/share/elasticsearch/config/elasticsearch.yml

⁠Portainer: Obtain and Setup

  1. Pull the docker image for portainer {bash} docker pull portainer/portainer
  2. Start Portainer using the following command [ NOTE ] This will setup a persistance directory in /tmp... It is advisable to change the mapping to something of your choosing {bash} docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/data portainer/portainer
  3. Open a web browser and navigate to http://<IP_OF_DOCKER_HOST>:9000
  4. Select the manage local Docker engine option
  5. Fill in the form for your preffered credentials
  6. Portainer should now be ready for use

⁠Portainer: Pulling an Image

  • Assuming you are logged in and Portainer is in working order, follow the next instructions
    1. On the left management pane click Images
    2. In the Pull Image section enter fuzzybunny/elastic:latest in the name field
    3. Click Pull and note the spinning gear as the image is downloaded
    4. When the image is downloaded, it should appear in theImages section on the bottom half of the screen

⁠Portainer: Create A Container

  1. On the left management pane click Containers
  2. Click the + Add container button
  3. In the name field, enter a suitable name
  4. Enter the image name in the Image field( this can be obtained throught Images menu )
  5. Deselect the Always pull the image option
  6. Use the Port Mapping: +map additional port to map ports to match the configuration section towards the top of this page
  7. Use the Advanced Container Settings section to finish configuring to match configuration section towards the top of this page
  8. Click Start container in the middle of the page
  9. Monitor the status of your container using the Container menu

⁠Changelog

⁠3 May 17
  • Abandoned custom deployment and moved to Portainer based infrastructure.. for trial
    • Removed dependencies on custom scripts
    • Added default configs inside image
    • Created Portainer instructions
⁠14 Apr 17
  • Changed packaging layout to be more maintainable( layout doesn't affect usage )
  • Enhanced start script to provision for more functionality ( help info start config remove )

Tag summary

Content type

Image

Digest

Size

98.8 MB

Last updated

over 9 years ago

docker pull fuzzybunny/elastic