Fresh repo use case

[nanikjava]

Tested with the following use-case:

Brand new repo with the following config

name: webhooktest
reference: main
working_dir: .
compose_files:
  - compose.yml
profiles:
  - debug
force_image_pull: true
force_recreate: true
destroy: true
destroy_opts:
  remove_images: true

doco-cd does not spin any containers due to the following block of code stopping the loop as it cannot find any running container.

		if deployConfig.Destroy {
			...

			// Check if doco-cd manages the project before destroying the stack
			containers, err := docker.GetLabeledContainers(ctx, dockerClient, filterLabel, deployConfig.Name)
			...

			// If no containers are found, skip the destruction step
			if len(containers) == 0 {
				....

				continue
			}
			...
		}

Combining force_image_pull and destroy in a single config does not work - are there any config that can work in this kind of use case ?

[kimdre]

destroy prevents doco-cd to deploy the stack. If you want to deploy the stack you need to set destroy: false .

[nanikjava]

This configuration

name: webhooktest
reference: main
working_dir: .
compose_files:
  - compose.yml
profiles:
  - debug
force_image_pull: true
force_recreate: true
destroy: false

works for a brand new repo as it will launch the container and download the image correctly.

Once a repo transition to not a new repo for every changes doco-cd download the latest image which is the correct behaviour however the local storage gets eaten up as the previous/old images are not removed.

What config can be used to instruct doco-cd to remove existing images ?

[kimdre]

This is currently not yet supported, but it will be soon. See the feature request: #814