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

./gradlew bootRun failed #66

Open
snowuyl opened this issue Oct 8, 2024 · 1 comment
Open

./gradlew bootRun failed #66

snowuyl opened this issue Oct 8, 2024 · 1 comment

Comments

@snowuyl
Copy link

snowuyl commented Oct 8, 2024

./gradlew bootRun
...
... 30 common frames omitted

Task :bootRun FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':bootRun'.

Process 'command '/usr/lib/jvm/java-17-openjdk-amd64/bin/java'' finished with non-zero exit value 1

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 11m 16s
4 actionable tasks: 4 executed

@robertmcnees
Copy link
Contributor

Hi @snowuyl. I ran through the guide and ./gradlew bootRun worked fine for me. I was able to then execute the curl commands for get and add as well. Perhaps it is an environment issue? I updated this guide with an Intel Mac and I just tested with an Apple silicon Mac.

The CI environment also looks clean, so I don't think it's a problem with the example code.

The guide requires a local docker environment to be available. Is Docker Desktop running? If I stop running Docker Desktop locally I get an error similar to what you posted. This was the stack trace above:

Stderr:
Cannot connect to the Docker daemon at unix:///Users/<my_user>/.docker/run/docker.sock. Is the docker daemon running?

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

2 participants