Simple Dockerfile examples are often broken by default

Re:Simple Dockerfile examples are often broken by default by j88439h84 on Tuesday May 28, 2019 @02:14PM (#20032787)

For reproducible builds, `python:3.7` isn't specific enough. python:3.7.3-alpine3.9 is more specific, for example. There aren't supposed to be breaking changes in the bugfix releases, but they'll happen anyway.

[ Parent | on HN ]

Re:Simple Dockerfile examples are often broken by default by kam on Tuesday May 28, 2019 @02:19PM (#20032830)

And `python:3.7@sha256:35ff9f44818f8850f1d318aa69c2e7ba61d85e3b93283078c10e56e7d864c183` is even better.

[ Parent | on HN ]

Re:Simple Dockerfile examples are often broken by default by meowface on Tuesday May 28, 2019 @07:28PM (#20035457)

Ran into this recently. Docker container was running into issues until I changed "python:3.7-alpine" to "python:3.7.3-alpine3.9". It was because a package I was relying on from "apk add" changed between Alpine versions.

I could probably safely make it "python:3.7-alpine3.9" (instead of pinning to Python 3.7.3), since the issue was the Alpine version, but at this point I'm starting to really buy into the whole reproducible build thing.

[ Parent | on HN ]

Re:Simple Dockerfile examples are often broken by default by mistrial9 on Tuesday May 28, 2019 @05:03PM (#20034381)

overfitting here?

[ Parent | on HN ]