Skip to content

docs(docker): Add OpenSearch backend stack to docker-compose #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 16 commits into from
Aug 1, 2025

Conversation

jamesfisher-geo
Copy link
Contributor

Some work is being done in stac-fastapi-elasticsearch-opensearch to support integration with stac-auth-proxy.

This PR adds the OpenSearch backend as an option in the docker-compose file

@alukach
Copy link
Member

alukach commented Jul 29, 2025

@jamesfisher-geo Thanks for putting this together! I'm out this week but will give it a try when I return.

@alukach alukach changed the title Add OpenSearch backend stack to docker-compose docs(docker): Add OpenSearch backend stack to docker-compose Jul 29, 2025
Copy link
Member

@alukach alukach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally, looks good. I proposed some refinements in AtomicMaps#2.

@jamesfisher-geo
Copy link
Contributor Author

Thanks @alukach! I tested your changes locally. When spinning up the os profiles after running the default docker-compose threw a build error

 => ERROR [internal] load build context                                                                                  0.0s
 => => transferring context: 57.61kB                                                                                     0.0s
 => CANCELED [stage-0 1/6] FROM docker.io/library/python:3.13-slim@sha256:4c2cf9917bd1cbacc5e9b07320025bdb7cdf2df7b0cea  0.1s
 => => resolve docker.io/library/python:3.13-slim@sha256:4c2cf9917bd1cbacc5e9b07320025bdb7cdf2df7b0ceaccb55e9dd7e309874  0.0s
 => => sha256:4c2cf9917bd1cbacc5e9b07320025bdb7cdf2df7b0ceaccb55e9dd7e30987419 9.12kB / 9.12kB                           0.0s
 => => sha256:a7cb177dc60dfa77b223192cd0d9e6ce1aac7cf9a569023d68e7c91b6371a718 1.75kB / 1.75kB                           0.0s
 => => sha256:38e57556b63539e63344b97f802e7cbd85b70e2087ee703e360fcdfe337cbbb3 5.43kB / 5.43kB                           0.0s
------
 > [internal] load build context:
------
failed to solve: error from sender: open /home/james/code/stac-auth-proxy/.pgdata: permission denied

I added .pgdata to a .dockerignore file, tested both again and it worked fine. Might be worth you trying both again locally before we merge this.

@jamesfisher-geo jamesfisher-geo requested a review from alukach August 1, 2025 15:51
@alukach
Copy link
Member

alukach commented Aug 1, 2025

I added .pgdata to a .dockerignore file, tested both again and it worked fine.

@jamesfisher-geo I didn't experience that issue. Will that change interfere with it being used as a volume?

volumes:
- ./.pgdata:/var/lib/postgresql/data

I also see that we aren't using a volume for OpenSearch. Perhaps it's not that important to retain .pgdata, I think the primary value is to persist data even if we tear down the docker images...

Copy link
Member

@alukach alukach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks again for adding this! Really helpful.

@alukach alukach merged commit d779321 into developmentseed:main Aug 1, 2025
1 check failed
@jamesfisher-geo
Copy link
Contributor Author

I added .pgdata to a .dockerignore file, tested both again and it worked fine.

@jamesfisher-geo I didn't experience that issue. Will that change interfere with it being used as a volume?

volumes:
- ./.pgdata:/var/lib/postgresql/data

I also see that we aren't using a volume for OpenSearch. Perhaps it's not that important to retain .pgdata, I think the primary value is to persist data even if we tear down the docker images...

Good point. My goal was to keep this as light as possible. Adding an opensearch volume is strait forward. We can simply copy the setup from SFEOS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants