I have forked an open source project and I would like to deploy it to ECS.

It has a docker-compose.yml .

Theoretically one can use such a file with ECS. But I have already run into three problems and I wonder if this is not really a reliable strategy. It seems to me that the ECS back-end for docker is poorly implemented.

I'll get to the main problem and you can skip the rambling after if you aren't interested in it.

The main problem is that I changed the docker-compose.yml to use ECR (because docker basically required me to). That works locally, but remotely I get:

$ docker --context default -D -l debug compose up 2>&1 | tee /tmp/logs_local.txt

FrontendTCP5173Listener  CreateComplete 
FrontendService  CreateInProgress 
FrontendService  CreateInProgress Resource creation Initiated
level=debug msg="Delete CloudFormation stack"
docsgpt  FrontendService EssentialContainerExited: Essential container in task exited
docsgpt  DeleteInProgress User Initiated
FrontendService  CreateFailed Resource creation cancelled
FrontendService  DeleteInProgress

I don't know how to get more information about the failure:

$ docker compose logs 
ResourceNotFoundException: The specified log group does not exist.

How do I figure out why the FrontendService exited?

===

That's the main problem. Here is the rambling about other problems that got me to this point which you can read or not, per your preference.

Starting from the original YML, it seems to require me to supply an image name in the iml instead of being able to just build into the cloud as in the original yml.

$  docker compose up
 WARNING [services.build](https://services.build): unsupported attribute
 service frontend doesn't define a Docker image to run: incompatible attribute

So I already need to change the docker-compose, which is at odds with Amazon's message that you can just use your docker-compose as-is.

This brings me to the next issue: even the slightest typo in the docker-compose.yml causes a silent failure. Which is horrible UX for a developer CLI. I can work around it, but it degrades my confidence in the tooling and makes me think that it might not be properly supported and implemented.

Anyhow, I want to add an image: line to my file.

It's unclear whether the images in my "default" local context are available in the "ecs" context because `docker compose images` says:

$ Command "compose images" not available in current context (awsdocgen). "not implemented"

Lots of commands are not implemented in this context. Another thing lowering my confidence level.

So I add the image: line to my file based on my local image ID: `image: 2d36783e9f21`

Now I get:

 INFO trying next host                              error="pull access denied, repository does not exist or may require authorization: server message: insufficient\_scope: authorization failed" [host=registry-1.docker.io](https://host=registry-1.docker.io)
pull access denied, repository does not exist or may require authorization:
server message: insufficient\_scope: authorization failed

I think it's trying to look for my image on docker hub, whereas I want it to use my local one.

So my second question is: Can I do this without using ECR and putting ECR image names in my docker-compose.yml?

Hi! I have an azure repo of a simple website that has a Dockerfile which I'm building with my Azure Pipelines

I want to publish that project into my aws ecs, and I was thinking of doing it with the azure pipelines releases, but since my account is free, it seems it doesn't have this option.

trigger:
  branches:
    include:
      - dev
      - prod

pool: my-laptop

variables:
  - name: imageName
    value: prueba
  - name: environment_name
    ${{ if eq(variables['Build.SourceBranchName'], 'dev') }}:
      value: dev
    ${{ if eq(variables['Build.SourceBranchName'], 'prod') }}:
      value: prod

stages:
  - stage: Build
    jobs:
    - job: Build
      displayName: Build Job
      steps:
      - task: Docker@2
        displayName: Build an image
        inputs:
          repository: $(imageName)
          command: build
          Dockerfile: Dockerfile

This is my pipeline for now.

Thank you!