Re-pin Docker base image in Dockerfile

[atomist]

This pull request re-pins the Docker base image node:lts in Dockerfile to the current digest.

https://github.com/atomist-skills/go-format-skill/blob/d5b0066788041350eee32ad9c50d2f124c495232/Dockerfile#L2-L2

Digest sha256:b9fe422fdf0d51f616d25aa6ccc0d900eb25ca08bd78d79e369c480b4584c3a8 references a multi-CPU architecture image manifest. This image supports the following architectures:

• sha256:f1a622bfdfdf4571fc9f774f0355080b1583a72ebd2c36ad00c169e4fc2a7270 linux/s390x

Changelog for node:lts

Commit

New image build caused by commit docker-library/official-images@22aa4e3 to library/node:

Node: feat: Node.js 18.7.0

---

Comparison

Comparing Docker image node:lts at digests

Current sha256:4e85818bd0d023d4f9025730dc0640d3d8269e3d1a84ce6365eca8fbad7a3ee9 (824mb) and
Proposed sha256:b9fe422fdf0d51f616d25aa6ccc0d900eb25ca08bd78d79e369c480b4584c3a8 (824mb):

Packages

No package differences detected

Files

The following file modifications were detected:

Name	Current	Proposed	Diff
/etc/apt/sources.list	416b	416b	0b
/etc/shadow	527b	527b	0b
/etc/shadow-	501b	501b	0b
/root/.gnupg/pubring.kbx	49kb	50kb	1.1kb
/root/.gnupg/pubring.kbx~	38kb	39kb	1.1kb
/root/.gnupg/random_seed	600b	600b	0b
/root/.gnupg/trustdb.gpg	1.2kb	1.2kb	0b
/root/.npm/_logs/2022-07-12T03_12_08_988Z-debug-0.log		-	0b
/root/.npm/_logs/2022-08-02T02_56_11_140Z-debug-0.log		+	1.5kb
/tmp/v8-compile-cache-0/9.4.146.24-node.21/zSoptzSyarn-v1.22.19zSbinzSyarn.js.BLOB	2.1mb	2.1mb	0b
/usr/lib/python3.7/__pycache__/_markupbase.cpython-37.pyc	7.6kb	7.6kb	0b
/usr/lib/python3.7/__pycache__/difflib.cpython-37.pyc	58kb	58kb	0b
/usr/lib/python3.7/__pycache__/ftplib.cpython-37.pyc	27kb	27kb	0b
/usr/lib/python3.7/__pycache__/hashlib.cpython-37.pyc	6.4kb	6.4kb	0b
/usr/lib/python3.7/__pycache__/netrc.cpython-37.pyc	3.7kb	3.7kb	0b
/usr/lib/python3.7/__pycache__/pathlib.cpython-37.pyc	41kb	41kb	0b
/usr/lib/python3.7/__pycache__/pydoc.cpython-37.pyc	83kb	83kb	0b
/usr/lib/python3.7/__pycache__/rlcompleter.cpython-37.pyc	5.6kb	5.6kb	0b
/usr/lib/python3.7/json/__pycache__/decoder.cpython-37.pyc	9.6kb	9.6kb	0b
/usr/local/share/fonts/.uuid	36b	36b	0b
/usr/share/fonts/.uuid	36b	36b	0b
/usr/share/fonts/truetype/.uuid	36b	36b	0b
/usr/share/fonts/truetype/dejavu/.uuid	36b	36b	0b
/usr/share/glib-2.0/codegen/__pycache__/codegen_docbook.cpython-37.pyc	12kb	12kb	0b
/var/cache/fontconfig/011d95e5-a065-4046-b409-7c365155b4d5-be64.cache-7		-	0b
/var/cache/fontconfig/2b9dd3b5-7c7d-4bec-9569-ebcf9bb05246-be64.cache-7		+	144b
/var/cache/fontconfig/60997158-f837-41b6-889e-23436d5bef97-be64.cache-7		-	0b
/var/cache/fontconfig/7ce16d4e-bba7-4b0d-b342-7c33f3562c4e-be64.cache-7		+	15kb
/var/cache/fontconfig/80990e79-8270-4519-9be5-a779c6051aca-be64.cache-7		-	0b
/var/cache/fontconfig/9d64548a-a7d8-4923-9d7b-d82b815e423e-be64.cache-7		-	0b
/var/cache/fontconfig/abef3e58-acfd-4ef0-ae98-a5e41691a353-be64.cache-7		+	160b
/var/cache/fontconfig/c7cc485e-0906-4c3d-82d2-ff9ed833a872-be64.cache-7		+	104b
/var/cache/ldconfig/aux-cache	15kb	15kb	0b
/var/log/alternatives.log	12kb	12kb	0b
/var/log/apt/eipp.log.xz	19kb	19kb	-4b
/var/log/apt/history.log	15kb	15kb	0b
/var/log/apt/term.log	81kb	81kb	0b
/var/log/dpkg.log	156kb	156kb	0b

History

The following differences in docker history were detected:

-/bin/sh -c #(nop) ADD file:b8babeb1255f220a475b65f77c9d786d49eda80433cab5dc00c944dc05d31c77 in /
+/bin/sh -c #(nop) ADD file:d4184c5029732fe05023927be89b0c768483920c072c2069f92b3f4912c1c09b in /
 /bin/sh -c #(nop)  CMD ["bash"]
 /bin/sh -c set -eux; 	apt-get update; 	apt-get install -y --no-install-recommends 		ca-certificates 		curl 		netbase 		wget 	; 	rm -rf /var/lib/apt/lists/*
 /bin/sh -c set -ex; 	if ! command -v gpg > /dev/null; then 		apt-get update; 		apt-get install -y --no-install-recommends 			gnupg 			dirmngr 		; 		rm -rf /var/lib/apt/lists/*; 	fi

Ports

No different exposed ports detected

Environment Variables

No different environment variables detected

---

Pinning FROM lines to digests makes your builds repeatable. Atomist will raise new pull requests whenever the tag moves, so that you know when the base image has been updated. You can follow a new tag at any time. Just replace the digest with the new tag you want to follow. Atomist, will switch to following this new tag.

---

File changed:

• Dockerfile

[atomist]

Pull request auto merged:

• No reviews
• 4 successful checks