Consider using node:16.17 instead of pulling the specific patch version number. If the image is versioned correctly, you'll always pull the latest version with patch fixes, which is what you generally want.
Many times I'll also just say node:16 (or python:3.10) and let it always pull the latest release for those major versions. I let the unit tests in my CI pipeline catch any breaking changes with the new container patch or minor version updates, just always run a docker pull node:16.17 when you do a dev build.
Consider using
node:16.17instead of pulling the specific patch version number. If the image is versioned correctly, you'll always pull the latest version with patch fixes, which is what you generally want.Many times I'll also just say
node:16(orpython:3.10) and let it always pull the latest release for those major versions. I let the unit tests in my CI pipeline catch any breaking changes with the new container patch or minor version updates, just always run adocker pull node:16.17when you do a dev build.Thank you for suggestion.