mammoth-garden-5368203/16/2023, 5:02 PM
provider repo, but I’m a bit confused as to whether this is a bug or a limitation of the provider itself so asking here for redundancy. I have an issue where I cannot download private images using the
resource because of permission errors ( docker CLI works fine) . I see no way to configure the resource to use explicit credentials (there’s configuration for pushing, though using the
resource) — how are credentials supposed to be propagated to the provider? ie this does not work out of the box with an auth’d docker CLI
airflow_image = RemoteImage( "airflow-2.3.0", name="<http://docker.io/myorg/airflow:v0.0.4|docker.io/myorg/airflow:v0.0.4>", ) airflow_scheduler_container = Container( "airflow-scheduler", image=airflow_image.image_id, command=["scheduler"], ports=[schedulerPorts], name="airflow-scheduler", envs=helpers.common_env(), restart="always", logs=True, ) ...