You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running docker compose up to start the services for the Registry on Linux, the elasticsearch service (confusingly named to start OpenSearch) exits with a failed status code.
This occurs on Red Hat Enterprise Linux release 8.7 (Ootpa), Debian GNU/Linux 11 (bullseye), and Linux Mint 20.3.
📜 To Reproduce
$ lsb_release --descriptionDescription: Linux Mint 20.3
$ docker compose versionDocker Compose version v2.14.1
$ docker compose --profile dev-api up --detach…
$ sleep 60
$ docker compose --profile dev-api ps | egrep Exiteddocker-elasticsearch-1 opensearchproject/opensearch:1.1.0 "./opensearch-docker…" elasticsearch About a minute ago Exited (0) 55 seconds ago
$ docker compose --profile dev-api logs --tail 4 elasticsearchdocker-elasticsearch-1 | For complete error details, refer to the log at /usr/share/opensearch/logs/docker-cluster.logdocker-elasticsearch-1 | Killing performance analyzer process 35docker-elasticsearch-1 | OpenSearch exited with code 1docker-elasticsearch-1 | Performance analyzer exited with code 143
$ echo the root cause seems to be …echo the root cause seems to be …
$ docker compose --profile dev-api logs elasticsearch | egrep 'Device or resource busy'docker-elasticsearch-1 | sed: cannot rename /usr/share/opensearch/config/sedERYoCV: Device or resource busy
🐛 Describe the bug
When running
docker compose up
to start the services for the Registry on Linux, theelasticsearch
service (confusingly named to start OpenSearch) exits with a failed status code.This occurs on Red Hat Enterprise Linux release 8.7 (Ootpa), Debian GNU/Linux 11 (bullseye), and Linux Mint 20.3.
📜 To Reproduce
🕵️ Expected behavior
📚 Version of Software Used
main
branch ofNASA-PDS/registry
pulled 2022-12-30 (3f6661c).🖥 System Info
🦄 Related requirements
⚙️ Engineering Details
The text was updated successfully, but these errors were encountered: