Docker & OpenSearch Engineer /w Fluentbit experience (with Ansible Integration Experience)
Budget: $15 – $25 USD
We’re seeking an experienced Docker and OpenSearch engineer to troubleshoot, stabilize, and optimize our current containerized OpenSearch deployment and help us build data-driven dashboards from Ansible patch reports.
Overview
Our environment runs on Linux with Docker Compose. OpenSearch and Dashboards containers launch correctly, but OpenSearch fails to recognize existing data even when the underlying data directory and permissions are intact. The containers are functional but need cleanup and configuration tuning to ensure smooth rebuilds and consistent JVM settings.
Environment
opensearch-node1: opensearchproject/opensearch:latest
Ports 9200 / 9600
Single-node cluster, security plugin disabled
Runs as UID 1000:1000 with mounted data & config volumes
Memory locking and JVM heap sizing (-Xms4g -Xmx4g) need to persist
dashboards: opensearchproject/opensearch-dashboards:latest
Port 5601, connected via Docker network
Compose file is stable but could use restructuring and optimization.
Core Objectives
Diagnose why OpenSearch doesn’t detect existing indices after container recreation, even with correct ownership.
Ensure data retention and persistent JVM configuration across restarts or upgrades.
Clean up and document the Docker Compose stack for long-term maintainability.
Build two OpenSearch dashboards sourced from Ansible patch logs (JSON) collected via cron/rsync from our control node:
One for Rocky Linux endpoints
One for Ubuntu endpoints
The Ansible job already runs automatically and generates structured JSON reports on patch results. These dashboards should visualize trends, successes, errors, and reboot requirements across user laptops.
Overview
Our environment runs on Linux with Docker Compose. OpenSearch and Dashboards containers launch correctly, but OpenSearch fails to recognize existing data even when the underlying data directory and permissions are intact. The containers are functional but need cleanup and configuration tuning to ensure smooth rebuilds and consistent JVM settings.
Environment
opensearch-node1: opensearchproject/opensearch:latest
Ports 9200 / 9600
Single-node cluster, security plugin disabled
Runs as UID 1000:1000 with mounted data & config volumes
Memory locking and JVM heap sizing (-Xms4g -Xmx4g) need to persist
dashboards: opensearchproject/opensearch-dashboards:latest
Port 5601, connected via Docker network
Compose file is stable but could use restructuring and optimization.
Core Objectives
Diagnose why OpenSearch doesn’t detect existing indices after container recreation, even with correct ownership.
Ensure data retention and persistent JVM configuration across restarts or upgrades.
Clean up and document the Docker Compose stack for long-term maintainability.
Build two OpenSearch dashboards sourced from Ansible patch logs (JSON) collected via cron/rsync from our control node:
One for Rocky Linux endpoints
One for Ubuntu endpoints
The Ansible job already runs automatically and generates structured JSON reports on patch results. These dashboards should visualize trends, successes, errors, and reboot requirements across user laptops.
Related categories:
Linux
Network Administration
Elasticsearch
Docker
Data Visualization
Ansible
Kibana
Docker Compose