Hacker News new | ask | show | jobs
by DistractionRect 1071 days ago
You can always build and tag your own docker image using the docker files included from source. Or simply follow the docker files as install instructions:

[0] https://github.com/photoprism/photoprism/blob/develop/docker...
1 comments
JamesonNetworks 1071 days ago
"simply follow the docker files"

I'm not sure if you perused the docker files for this repo, but imho there is nothing simple about them

Edit:

I was curious so I dug into them a bit and found that the dockerfile references a develop docker image. There is a second docker file to see how that base image is built. In the steps to build that base image, we grab some .zip files from the web for the AI models. We install go, nodejs, mariadb, etc for quite a few deps, and then there is also a substantial list of packages installed. One step also does:

  apt-get update && apt-get -qq dist-upgrade
Which seems a bit iffy to me. Each step calls a script which in turn has its own steps. Overall, I'd say the unfurled install script would be quite long and difficult to grok. Also, I'm not saying any of this is "bad," but it is complex.
link
the_common_man 1071 days ago
dist upgrade in a Dockerfile?
link
wiredfool 1071 days ago
Yes. That just means upgrade and install extra required packages.

The nonsensical one would be do-release-upgrade.

link
411111111111111 1071 days ago
They're both kinda dumb though. Updating will create a new layer, but the old binaries will still be a part of the image as part of the history.

The only correct way is to either rebuild the base image from scratch or just fetch a new base image. My suggestion would be the latter, just run docker pull again for the baseimage and use that, without running update.

link