@@ -434,14 +434,13 @@ The containers have the proxy as an `ENTRYPOINT` so, to use the proxy from a
434434container, all you need to do is specify options using the command, and expose
435435the proxy' s internal port to the host. For example, you can use:
436436
437- <!-- {x-release-please-start-version} -->
438437```shell
439438docker run --publish <host-port>:<proxy-port> \
440- gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.12.0 \
441- --address "2.12 .0.0" --port <proxy-port> <instance-connection-name>
439+ gcr.io/cloud-sql-connectors/cloud-sql-proxy:latest \
440+ --address "0.0 .0.0" --port <proxy-port> <instance-connection-name>
442441```
443442
444- You' ll need the ` --address " 2.12 .0.0" ` so that the proxy doesn' t only listen for
443+ You' ll need the ` --address " 0.0 .0.0" ` so that the proxy doesn' t only listen for
445444connections originating from *within* the container.
446445
447446You will need to authenticate using one of the methods outlined in the
@@ -465,12 +464,11 @@ For example, a full command using a JSON credentials file might look like
465464docker run \
466465 --publish <host-port>:<proxy-port> \
467466 --mount type=bind,source="$(pwd)"/sa.json,target=/config/sa.json \
468- gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.12.0 \
469- --address 2.12 .0.0 \
467+ gcr.io/cloud-sql-connectors/cloud-sql-proxy:latest \
468+ --address 0.0 .0.0 \
470469 --port <proxy-port> \
471470 --credentials-file /config/sa.json <instance-connection-name>
472471```
473- <!-- {x-release-please-end} -->
474472
475473## Running as a Kubernetes Sidecar
476474
0 commit comments