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
Alternatively credentials can be set as environment variables. Environment variables take precedence over the Docker credentials store. Environment variables can be specified with or without a server name. The variant without a server name takes precedence.
121
+
122
+
This is intended for running `docker-pushrm` as a standalone tool in a CI environment (no full Docker installation needed).
123
+
124
+
-`DOCKER_USER` and `DOCKER_PASS`
125
+
-`DOCKER_USER__<SERVER>_<DOMAIN>` and `DOCKER_PASS__<SERVER>_<DOMAIN>`
126
+
(example for server `docker.io`: `DOCKER_USER__DOCKER_IO=my-user` and `DOCKER_PASS__DOCKER_IO=my-password`)
127
+
128
+
The provider 'quay' needs an additional env var for the API key in form of `APIKEY__<SERVERNAME>_<DOMAIN>=<apikey>`.
In the Docker config file (default: `$HOME/.docker/config.json`) add a json key `plugins.docker-pushrm.apikey_<servername>` with the api key as string value.
@@ -144,7 +164,7 @@ You can still use `docker-pushrm` as standalone executable.
144
164
145
165
The only obstacle is that you need to provide it credentials in the Docker style.
146
166
147
-
The easiest way for that is to set up a minimal Docker config file with the registry server logins that you need.
167
+
The easiest way for that is to set up a minimal Docker config file with the registry server logins that you need. (Alternatively credentials can be passed [in environment variables](#log-in-with-environment-variables-for-ci) )
148
168
149
169
You can either create this config file on a computer with Docker installed (by running `docker login` and then copying the `$HOME/.docker/config.json` file).
0 commit comments