Christopher Farnham

@wwuck Could you provide a small example of the multi-stage build with the single RUN that avoides docker caching?

Here is a slightly redacted snippet of our fleet.yaml ``` helm: releaseName: x-service timeoutSeconds: 600 waitForJobs: true chart: "oci://docker.xxxx.com/xxx-ecr/charts/x-service" version: '0.1.x-x' values: {} valuesFiles: [] valuesFrom: - configMapKeyRef: name: x-service-values...

I'll have to try the `--password-file` approach tomorrow morning. Oddly, this seems to work in our local development environments on our Mac laptops. But the CI failures are in our...

To test in an environment I have more control over I used the following Dockerfile to create an image configured similar to our CI image: ``` FROM ubuntu:latest RUN apt-get...

Here's the bundle the above is referencing, which I've redacted slightly ``` defaultNamespace: service namespaceLabels: local-secrets: "true" dependsOn: - selector: matchLabels: bundle: kafka - selector: matchLabels: bundle: cloudnative-pg helm: releaseName:...

FWIW - I believe that what we have been experiencing here is a variant of this issue https://github.com/rancher/fleet/issues/3560 We'll be watching that issue closely and add more information if necessary.

I'd just like to say that graceful handling of unreachable chart URLs would be really helpful for us. It would allow us to test bundle deployments in a dev environment...