Description:

When deploying my backend GraphQl engine using svc deploy, it is failing to deploy when using the hasura/graphql-engine:v2.1.1.cli-migrations-v3 image. When another member of the team follows the same step, they can deploy with no errors.

If I change the image to, for example, hasura/graphql-engine:v2.0.7 then the image backend will deploy.

However, I am now facing a similar issue when running svc deploy in my Maven Java backend service folder where I am using: FROM maven:3.8.3-openjdk-17-slim AS build and FROM openjdk:17-slim

The Docker file used is:

#!/bin/bash
FROM maven:3.8.3-openjdk-17-slim AS build
RUN mkdir -p /workspace
WORKDIR /workspace
COPY pom.xml /workspace
COPY src /workspace/src

RUN mvn -B -f pom.xml clean package -DskipTests

#!/bin/bash
FROM openjdk:17-slim
EXPOSE 8082
COPY --from=build /workspace/target/*.jar app.jar
RUN apt-get update && apt-get install -y curl
HEALTHCHECK --interval=25s --timeout=3s --start-period=50s --retries=3 \\
  CMD curl -f <http://localhost:8082/actuator/health> || exit 1
ENTRYPOINT ["java","-jar","app.jar"]

Expected outcome if steps followed:

ECS should have a new revision of task altra-test-export which is active

Actual outcome if steps are followed:

For the GraphQl engine, before the fix, the following error was occurring when trying to run svc deploy

  | 2022-01-19T10:49:27.907+00:00Copystandard_init_linux.go:228: exec user process caused: exec format error | standard_init_linux.go:228: exec user process caused: exec format error
-- | -- | --

After googling, I found this issue and decided to change FROM hasura/graphql-engine:v2.1.1.cli-migrations-v3 to FROM hasura/graphql-engine:v2.0.7, the app now deploys and the following new error occurs:

The current issue for the maven project has the following error appear when svc deploy is run.

copilot/export/58577c160d standard_init_linux.go:228: 
exec user process caused: exec format error

Solutions attempted so far: