Has Dragonfly 2.2.0 and its corresponding Helm chart 1.2.29 no longer support Docker runtime? Just the documents are no longer supported? Or is it that the software itself no longer supports Docker runtime?

[zsksy123]

I read in the document that starting from Dragonfly 2.2.0, Docker containerRuntime is no longer supported. I'm a little confused. Is it that the document is no longer supported? Or is it that we can no longer use Docker for image acceleration?
Can the helm chart version 1.4.2 (app version 2.3.0) utilize the docker containerRuntime?

I found that the containerRuntime configuration had been moved to the "client.config" section and the default configurations had been deleted. So, I simply moved the old configuration to "client.config".

Is the following configuration correct?

client:
    config:
      containerRuntime:
        docker:
          enable: true
          restart: false
          skipHosts:
            - "127.0.0.1"
            - "docker.io"
            - "ghcr.io"
          injectHosts: true
          insecure: false
          registryDomains:
            - "quay.io"
          registryPorts:
            - 443
          caCert:
            countryName: CN
            stateOrProvinceName: Hangzhou
            localityName: Hangzhou
            organizationName: Dragonfly
            commonName: "Dragonfly Authority CA"

Or in other words, by using this version, I will no longer provide support for Docker. Even if I have configured it, Docker still cannot be accelerated using Dragonfly?

[gaius-qi]

@zsksy123 It is not recommended to use docker daemon for runtime. If you must use it, please refer to https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/values.yaml#L1289.

[zsksy123]

@gaius-qi Thank you. It means that you can use versions of Dragonfly 2.2.0 or later to accelerate Docker images. But the configuration is simply to manually configure the Docker proxy on the host machine, right? Is there no need to make any configuration in the values.yaml file?