You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dont think this is a defect in this plugin, but it might be worth noting in the documentation:
I have a setup for my dev environment where i have a private docker registry running that holds my docker images using a self-signed cert. When using the docker-image resource types, you provide the cert in the pipeline definition so that it can build push the images to the registry. This works because docker is running in the concourse worker container. However, when using this docker-compose resource type, if you are running docker compose against a remote docker host, that certificate has to be installed on that remote host, or docker compose will not be able to pull images from the private registry. It will not use the cert provided in the pipeline file in the ca_certs configuration for the private registry. Might be obvious to people more familiar with docker but it took me a little bit to sort out.
The text was updated successfully, but these errors were encountered:
I dont think this is a defect in this plugin, but it might be worth noting in the documentation:
I have a setup for my dev environment where i have a private docker registry running that holds my docker images using a self-signed cert. When using the docker-image resource types, you provide the cert in the pipeline definition so that it can build push the images to the registry. This works because docker is running in the concourse worker container. However, when using this docker-compose resource type, if you are running docker compose against a remote docker host, that certificate has to be installed on that remote host, or docker compose will not be able to pull images from the private registry. It will not use the cert provided in the pipeline file in the ca_certs configuration for the private registry. Might be obvious to people more familiar with docker but it took me a little bit to sort out.
The text was updated successfully, but these errors were encountered: