I’m a little confused on the “remote docker” stuff. In this more or less real world scenario, let’s say I start a build on image
Within my config, imagine I have a step like
- image: myorg/deploy
- [auth against private registry]
- docker build ...
- docker push pri.vate/foo/someotherimage
In this scenario, am I good, assuming the base I’m building on is also a private image, not
myorg/deploy? What about if the base is a Dockerhub image, but I’m pushing to a private image? In this case, I assume that authing is better; does running an auth step in the main container accomplish this for the remote docker engine (I assume so, since it does work for our private registry).
In other words, does the caveat about this not applying to remote docker require additional auth? Does
setup_remote_docker itself also take or require auth params?