Docker Image 3.1.1 doesn't seem to work

OpenSearch
21

Pretty much the same position here.

So there’s a breaking change in 3.0.0 to 3.1.0 when running on Alma 8.10, probably JAVA related.

Anyone been able to test on Alma v9?

22

@Crickes Alma9.6 is fine.

[pablo@localhost ~]$ curl --insecure -u admin:Eliatra123 https://localhost:9200
{
  "name" : "opensearch-node1",
  "cluster_name" : "opensearch-cluster",
  "cluster_uuid" : "J2s85ndgS5Oo3T-sr1nibA",
  "version" : {
    "distribution" : "opensearch",
    "number" : "3.1.0",
    "build_type" : "tar",
    "build_hash" : "8ff7c6ee924a49f0f59f80a6e1c73073c8904214",
    "build_date" : "2025-06-21T08:05:43.345081313Z",
    "build_snapshot" : false,
    "lucene_version" : "10.2.1",
    "minimum_wire_compatibility_version" : "2.19.0",
    "minimum_index_compatibility_version" : "2.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}
[pablo@localhost ~]$ cat /etc/*release
AlmaLinux release 9.6 (Sage Margay)
NAME="AlmaLinux"
VERSION="9.6 (Sage Margay)"
ID="almalinux"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.6"
PLATFORM_ID="platform:el9"
PRETTY_NAME="AlmaLinux 9.6 (Sage Margay)"
ANSI_COLOR="0;34"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos"
HOME_URL="https://almalinux.org/"
DOCUMENTATION_URL="https://wiki.almalinux.org/"
BUG_REPORT_URL="https://bugs.almalinux.org/"

ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9"
ALMALINUX_MANTISBT_PROJECT_VERSION="9.6"
REDHAT_SUPPORT_PRODUCT="AlmaLinux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.6"
SUPPORT_END=2032-06-01
AlmaLinux release 9.6 (Sage Margay)
AlmaLinux release 9.6 (Sage Margay)
[pablo@localhost ~]$
23

@Crickes Good news. I’ve found the way to run it in AlmaLinux8.
In short AlmaLinux8 is running on kernel 4.18 by default. AlmaLinux9 is on 5.x

I’ve installed kernel 5.4 on AlmaLinux8 and OpenSearch started successfully.

image
image1109×234 12.1 KB

[root@localhost pablo]# curl --insecure -u admin:Eliatra123 https://localhost:9200
{
  "name" : "opensearch-node1",
  "cluster_name" : "opensearch-cluster",
  "cluster_uuid" : "BTKf7poWR3OosXwDZQ07og",
  "version" : {
    "distribution" : "opensearch",
    "number" : "3.1.0",
    "build_type" : "tar",
    "build_hash" : "8ff7c6ee924a49f0f59f80a6e1c73073c8904214",
    "build_date" : "2025-06-21T08:05:43.345081313Z",
    "build_snapshot" : false,
    "lucene_version" : "10.2.1",
    "minimum_wire_compatibility_version" : "2.19.0",
    "minimum_index_compatibility_version" : "2.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

[root@localhost pablo]# cat /etc/*release
AlmaLinux release 8.10 (Cerulean Leopard)
AlmaLinux release 8.10 (Cerulean Leopard)
NAME="AlmaLinux"
VERSION="8.10 (Cerulean Leopard)"
ID="almalinux"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="AlmaLinux 8.10 (Cerulean Leopard)"
ANSI_COLOR="0;34"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:almalinux:almalinux:8::baseos"
HOME_URL="https://almalinux.org/"
DOCUMENTATION_URL="https://wiki.almalinux.org/"
BUG_REPORT_URL="https://bugs.almalinux.org/"

ALMALINUX_MANTISBT_PROJECT="AlmaLinux-8"
ALMALINUX_MANTISBT_PROJECT_VERSION="8.10"
REDHAT_SUPPORT_PRODUCT="AlmaLinux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.10"
SUPPORT_END=2029-06-01
AlmaLinux release 8.10 (Cerulean Leopard)
AlmaLinux release 8.10 (Cerulean Leopard)

[root@localhost pablo]# uname -r
5.4.295-1.el8.elrepo.x86_64
24

Pablo,

Thank you for taking the time to test and feed this information back, it really is appreciated.

The issue that I, and I suspect others have, is that we are running on managed infrastructure and we don’t get to update Kernel versions or indeed set the schedule for upgrade to newer version of the OS.

It’s great to learn that Alma9 and Alma10 have a kernel which can run the newest version of OpenSearch, but until the managed infrastructure we use has caught up and upgraded, we’re going to be stuck at OpenSearch 3.0.0., unless we can find a way of modifying the OpenSearch code/config to remove the change that causing this to fail.

Any ideas what changes in OpenSearch 3.1.x that may have caused this breaking change?

Steve

25

@Crickes I had impression that you’re running your AlmaLinux8 VM with VMware on-prem solution.

Unfortunately, I couldn’t find anything related in the release notes.
I get the same behaviour on the vanilla AlmaLinux8 with OpenSearch minimal binary installation.

At this point, I can only suggest filing an issue in the OpenSearch GitHub. If you do so, please share the link here for traceability.

26

I’ve created an issue in the OpenSearch GitHub.

2 Likes
27

I ran into the same issue with RHEL 8.10 which is an enterprise linux based on the kernel 4.18.0.
Thanks for creating an issue on GitHub @pablo !

1 Like