paketo-buildpacks / opentelemetry

Apache License 2.0
19 stars 0 forks source link

Exec format error #151

Open piotrblasiak opened 1 day ago

piotrblasiak commented 1 day ago

I am building a docker image using the spring boot maven plugin with this config:

<plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
                <configuration>
                    <image>
                        <name>XXXX.amazonaws.com/${project.artifactId}:${project.version}</name>
                        <buildpacks>
                            <buildpack>paketo-buildpacks/java</buildpack>
                            <buildpack>gcr.io/paketo-buildpacks/opentelemetry</buildpack>
                        </buildpacks>
                        <env>
                            <BP_JVM_VERSION>${java.version}</BP_JVM_VERSION>
                            <BP_ARCH>amd64</BP_ARCH>
                            <BP_OPENTELEMETRY_ENABLED>true</BP_OPENTELEMETRY_ENABLED>
                        </env>
                    </image>
                </configuration>
            </plugin>

But when deploying it in kubernetes (m7a instances) I get:

Calculated JVM Memory Configuration: -XX:MaxDirectMemorySize=10M -Xmx2526992K -XX:MaxMetaspaceSize=378975K -XX:ReservedCodeCacheSize=240M -Xss1M (Total Memory: 3417968K, Thread Count: 250, Loaded Class Count: 64495, Headroom: 0%)
Enabling Java Native Memory Tracking
Adding 146 container CA certificates to JVM truststore
Spring Cloud Bindings Enabled
ERROR: failed to launch: exec.d: failed to execute exec.d file at path '/layers/paketo-buildpacks_opentelemetry/helper/exec.d/properties': fork/exec /layers/paketo-buildpacks_opentelemetry/helper/exec.d/properties: exec format error
dmikusa commented 1 day ago

See https://github.com/orgs/paketo-buildpacks/discussions/312#discussioncomment-10846153

more detail and background here too -> https://github.com/paketo-buildpacks/java/discussions/1387#discussioncomment-9733781