You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Im trying to instrument a Spring Boot application deployed on AWS ECS Fargate with the agent. Running the container with ENTRYPOINT ["java", "-jar", "app.jar"] works, but the moment I try to add the agent, it fails to start with the following error: /bin/sh: 1: [java,: not found. Completely stuck at what could be causing the issue.
Agent version: latest
Spring Boot version: 3.1.2
JDK version: Eclipse Temurin 17
Dockerfile:
FROM eclipse-temurin:17-jdk-jammy as builder
COPY build.gradle settings.gradle gradlew ./
COPY gradle/ gradle/
RUN chmod +x ./gradlew
COPY . .
RUN ./gradlew assemble
FROM eclipse-temurin:17-jdk-jammy
WORKDIR /app
EXPOSE 3000
# DataDog agent setupRUN apt-get update
RUN apt-get install wget -y
RUN wget -O dd-java-agent.jar 'https://dtdg.co/latest-java-tracer'COPY --from=builder /app/build/libs/app.jar /app/app.jar
ENTRYPOINT ["java", "-javaagent:dd-java-agent.jar""-jar", "app.jar"]
Task Definition (edited non-relevant sections):
A very similar configuration for the datadog-agent and log-forwarder containers works for our Node applications, not sure if Java needs additional configuration.
Oh man,so embarrassing, haha. Yea that was definitely it! Thanks for that, all containers are running now.
Unfortunately I´m not seeing the app getting registered in DataDog, also the API Key associated shows "No recent usage". Not sure if something is missing
Hi, Im trying to instrument a Spring Boot application deployed on AWS ECS Fargate with the agent. Running the container with
ENTRYPOINT ["java", "-jar", "app.jar"]
works, but the moment I try to add the agent, it fails to start with the following error:/bin/sh: 1: [java,: not found
. Completely stuck at what could be causing the issue.A very similar configuration for the
datadog-agent
andlog-forwarder
containers works for our Node applications, not sure if Java needs additional configuration.The text was updated successfully, but these errors were encountered: