-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Elasticsearch Dev Services gives Operation not permitted
on startup when using Podman
#31960
Comments
/cc @geoand (devservices), @gsmet (elasticsearch), @loicmathieu (elasticsearch), @stuartwdouglas (devservices), @yrodiere (elasticsearch) |
This does seem specific to podman, though caused by a bug in the ES container: elastic/cloud-on-k8s#5212 It would seem Elasticsearch 8 isn't affected anymore, in which case moving to ES 8 as the default would solve the problem. Can you try setting this, see if that helps?
|
I did try that initially but got some other error, but let me try again. I'll report back here |
Please see the PR for response on upgrade to v8 |
Note a workaround is to use ES 8 in dev services through this configuration property:
And if you're using Hibernate Search, don't forget to update the version expected by Hibernate Search as well:
It will complain as it doesn't know of Elasticsearch 8, but I don't know of any actual bugs, so it should be fine. |
Operation not permitted
on startupOperation not permitted
on startup when using Podman
Interestingly, elasticsearch wasn't one of the tests that failed when on the first run of the Linux Quarkus CI. Does this mean we have a test coverage issue, or is this fixed by another change? |
This is not fixed as far as I know. And Elasticsearch did start in your run:
Maybe this run does not use podman everywhere? EDIT: Or maybe podman is configured differently on CI. |
That's a good point, @yrodiere, if we can see elasticsearch start, it's not a coverage problem. :) It could be a version difference, since we seem to have several podman-related issues where it works on one version and then doesn't work on a different dot version. I suspect OS also makes a difference, but here CI and the initial issue are both Linux. It could also be a rootfuliness issue. I'm seeing some differences in the opposite direction, too, where things fail on the Podman CI but pass locally. This is the version info from the CI
|
Describe the bug
When starting up a app that uses elasticsearch dev services I get:
chroot: cannot change root directory to '/': Operation not permitted
I am using podman, not sure if that is the issue.
Expected behavior
Elasticsearch should start
Actual behavior
It does not
How to Reproduce?
No response
Output of
uname -a
orver
Linux pkruger-laptop 6.1.18-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Mar 11 16:09:14 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
openjdk version "17.0.6" 2023-01-17
OpenJDK Runtime Environment (Red_Hat-17.0.6.0.10-1.fc37) (build 17.0.6+10)
OpenJDK 64-Bit Server VM (Red_Hat-17.0.6.0.10-1.fc37) (build 17.0.6+10, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
999-SNAPSHOT
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/Maven/apache-maven-3.8.5
Java version: 17.0.6, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-17-openjdk-17.0.6.0.10-1.fc37.x86_64
Default locale: en_AU, platform encoding: UTF-8
OS name: "linux", version: "6.1.18-200.fc37.x86_64", arch: "amd64", family: "unix"
Additional information
Output of
docker -v
is:podman version 4.4.2
The text was updated successfully, but these errors were encountered: