docker-archive / compose-cli

Easily run your Compose application to the cloud with compose-cli
Apache License 2.0
955 stars 253 forks source link

docker compose up does not create new task on same image tag #2147

Closed Minipada closed 1 year ago

Minipada commented 2 years ago

Description I have a docker compose file in which I run different services. Each with a tag XXX.dkr.ecr.us-east-1.amazonaws.com/IMAGE:prod

This image gets updated before deploying but the tag is the same. When running docker-compose up, no new task is created even though a new tag has been created.

I tried doing a docker convert to see what the Cloudformation would be: image

But my task definition is not using the same hash image

Is it a bad pattern or a solution?

Steps to reproduce the issue:

  1. docker compose up
  2. deploy
  3. docker compose up

Describe the results you received: No new deployment is done

Describe the results you expected: A new deployment is done

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker-compose --version:

$ docker compose version                                                                
Docker Compose version dev

Output of docker version:

Client:
 Cloud integration: v1.0.24
 Version:           20.10.14
 API version:       1.41
 Go version:        go1.18
 Git commit:        a224086349
 Built:             Thu Mar 24 08:56:17 2022
 OS/Arch:           linux/amd64
 Context:           windrose-dashboard-staging
 Experimental:      true

Server:
 Engine:
  Version:          20.10.14
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18
  Git commit:       87a90dc786
  Built:            Thu Mar 24 08:56:03 2022
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.6.2
  GitCommit:        de8046a5501db9e0e478e1c10cbcfb21af4c6b2d.m
 runc:
  Version:          1.1.1
  GitCommit:        
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker context show:
You can also run docker context inspect context-name to give us more details but don't forget to remove sensitive content.

[
    {
        "Name": "windrose-dashboard-staging",
        "Metadata": {
            "Type": "ecs"
        },
        "Endpoints": {
            "docker": {
                "SkipTLSVerify": false
            },
            "ecs": {
                "Profile": "default"
            }
        },
        "TLSMaterial": {},
        "Storage": {
            "MetadataPath": hidden
            "TLSPath": hidden
        }
    }
]

Output of docker info:

not available on ECS

Otherwise

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.8.1-docker)
  compose: Docker Compose (Docker Inc., v2.2.3)

Server:
 Containers: 7
  Running: 7
  Paused: 0
  Stopped: 0
 Images: 11
 Server Version: 20.10.14
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: false
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: de8046a5501db9e0e478e1c10cbcfb21af4c6b2d.m
 runc version: 
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.15.32-1-MANJARO
 Operating System: Manjaro Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 31.23GiB
 Name: david
 ID: 4J7F:LTV6:ILSK:7HNW:YGV7:W5CP:KG4R:7NKO:ENWD:7VCA:FW3S:WWX7
 Docker Root Dir: /home/david/docker
 Debug Mode: false
 Username: dbensoussan
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  brisa-acer.local:5000
  127.0.0.0/8
 Live Restore Enabled: false
stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 1 year ago

This issue has been automatically closed because it had not recent activity during the stale period.