Update default docker compose BOULDER_TOOLS_TAG (#6995)

This is a follow-up fix to
https://github.com/letsencrypt/boulder/pull/6987 which mistakenly did
not update the docker compose default BOULDER_TOOLS_TAG variable from
go1.20.5 to go1.20.6. This would only manifest on developer machines
manually running unit/integration tests rather than CI which explicitly
tests against a matrix of BOULDER_TOOLS_TAG versions.
```
Error response from daemon: manifest for letsencrypt/boulder-tools:go1.20.5_2023-07-11 not found: manifest unknown: manifest unknown
```
This commit is contained in:
Phil Porada 2023-07-12 16:18:25 -04:00 committed by GitHub
parent b090ffbd2e
commit 4ea8362e90
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -2,7 +2,7 @@ version: '3'
services: services:
boulder: boulder:
# Should match one of the GO_DEV_VERSIONS in test/boulder-tools/tag_and_upload.sh. # Should match one of the GO_DEV_VERSIONS in test/boulder-tools/tag_and_upload.sh.
image: &boulder_image letsencrypt/boulder-tools:${BOULDER_TOOLS_TAG:-go1.20.5_2023-07-11} image: &boulder_image letsencrypt/boulder-tools:${BOULDER_TOOLS_TAG:-go1.20.6_2023-07-11}
environment: environment:
# To solve HTTP-01 and TLS-ALPN-01 challenges, change the IP in FAKE_DNS # To solve HTTP-01 and TLS-ALPN-01 challenges, change the IP in FAKE_DNS
# to the IP address where your ACME client's solver is listening. # to the IP address where your ACME client's solver is listening.