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

Error when building GradleDockerfile #157

Closed
cinorthstarmls opened this issue May 4, 2023 · 3 comments · Fixed by #158
Closed

Error when building GradleDockerfile #157

cinorthstarmls opened this issue May 4, 2023 · 3 comments · Fixed by #158
Assignees
Labels
bug Something isn't working DevOps
Milestone

Comments

@cinorthstarmls
Copy link

I'm encountering an error when trying to build the GradleDockerfile (On MacOS). Any help would be greatly appreciated.
Command:
docker build --file GradleDockerfile -t web-api-commander-gradle .

Error:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000000002b1c0, pid=43, tid=47
#
# JRE version: OpenJDK Runtime Environment (17.0.7+7) (build 17.0.7+7-alpine-r0)
# Java VM: OpenJDK 64-Bit Server VM (17.0.7+7-alpine-r0, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
# Problematic frame:
# C  [libnative-platform-file-events.so+0x2eb8c]  _init+0x39e4
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /root/.gradle/daemon/7.6.1/hs_err_pid43.log
#
# If you would like to submit a bug report, please visit:
#   https://gitlab.alpinelinux.org/alpine/aports/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#


* 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
@darnjo
Copy link
Member

darnjo commented May 8, 2023

Hi there. Thanks for reporting this.

What kind of Mac are you on? I was able to build the container successfully on an Air M2.

image

image

We have pre-built containers if that helps.

@cinorthstarmls
Copy link
Author

I'm also using a Mac M2. Since this is my first build, it's completely fresh. Is it possible that your docker build cache is being used instead of totally rebuilding the image?

Is the pre-built image stored in a public registry? How can I access it?

@darnjo
Copy link
Member

darnjo commented May 8, 2023

I'll look into the local build.

You can find the ECR image here.

@darnjo darnjo self-assigned this May 10, 2023
@darnjo darnjo added bug Something isn't working DevOps labels May 10, 2023
@darnjo darnjo added this to the Backlog milestone May 10, 2023
@darnjo darnjo linked a pull request May 10, 2023 that will close this issue
darnjo pushed a commit that referenced this issue Aug 29, 2023
darnjo pushed a commit that referenced this issue Aug 29, 2023
darnjo pushed a commit that referenced this issue Aug 29, 2023
darnjo pushed a commit that referenced this issue Sep 4, 2023
darnjo pushed a commit that referenced this issue Sep 4, 2023
darnjo added a commit that referenced this issue Sep 4, 2023
* Update GradleDockerfile

* Bump to OpenJDK11

* Updated Dockerfile

* Update Commander utils to use OpenJDK 11.

* #157: Updated GradleDockerfile to run current ./gradlew with OpenJDK11

* #157: Parameterized GradleDockerfile

* #157: Removed unnecessary build command

* #157: Updated .dockerignore

* #157: Switched to different OpenJDK source (old one deprecated) and tidied up build

* #157: Updated README

---------

Co-authored-by: darnjo <josh@reso.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working DevOps
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants