Skip to content
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

"Please set the JAVA_HOME variable" since update #513

Open
1 of 2 tasks
rowie opened this issue Apr 5, 2024 · 6 comments
Open
1 of 2 tasks

"Please set the JAVA_HOME variable" since update #513

rowie opened this issue Apr 5, 2024 · 6 comments

Comments

@rowie
Copy link

rowie commented Apr 5, 2024

The problem

Since update to the lattest docker version i got this:

{"error":"ERROR: JAVA_HOME is set to an invalid directory: /opt/java/openjdk
Please set the JAVA_HOME variable in your environment to match the location of your Java installation

Are you using the latest released version?

  • Yes

Have you read the troubleshooting page?

  • Yes

What type of installation are you running?

signal-cli-rest-api Docker Container

In which mode are you using the docker container?

Normal Mode

What's the architecture of your host system?

x86-64

Additional information

No response

@bbernhard
Copy link
Owner

When do you get that error? I do not see that issue here.

@viaregio
Copy link

viaregio commented May 2, 2024

I'm not the issue owner, but I get the same error whiel calling signal-cli from within the container.

I called signal-cli from within the container to understand why all endpoints give me a status of 400.

@bbernhard
Copy link
Owner

I'm not the issue owner, but I get the same error whiel calling signal-cli from within the container.

I called signal-cli from within the container to understand why all endpoints give me a status of 400.

Which mode do you use?

@viaregio
Copy link

viaregio commented May 3, 2024

I use the native mode.

@viaregio
Copy link

viaregio commented May 3, 2024

Setting JAVA_HOME=/lib/jvm/java-21-openjdk-amd64 and modifying the path accordingly fixed the problem for me.

@jounathaen
Copy link

Same issue and @viaregio's solution fixes it. (until Java 22 is used in the container 😅 )

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

No branches or pull requests

4 participants