Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DA
Posts
1
Comments
63
Joined
2 yr. ago

  • Desktop: Macintosh (<X) -> Windows (XP-10) w/occasional Ubuntu dual-boot (various DEs) -> Debian + Gnome

    Server: Ubuntu LTS -> Debian

    I’ve also had a number of used thinkpads over the years where I mostly ran Xubuntu and crunchbang.

    I still boot into Windows every month or so if I need to model something in Rhino (CAD). Couldn’t get it working in Wine and my 12 YO computer isn’t performant enough to run it in a VM. The last thread remaining and waiting to be cut…

  • I remember getting a Ubuntu CD box set many years ago when I ordered free disks in the mail as a teenager. The box was well constructed, prints of high quality and the CD labels were especially sharp.

    Crazy how physical media was king back then.

  • Am I understanding correctly that you are building the image by copying in key elements from the host machine’s functioning nginx installation?

    This is creative but not common approach to docker.

    Normally software is installed following the officially documented procedure (imagine installing using apt or a shell script via RUN). Sometimes software documentation has specific recommendations to follow for containerized installs.

    It’s common to have the version defined as a variable where a change in value invalidates the docker layer cache. To me it’s unclear how caching would work with your dockerfile, for example, in the event of a upgrade. You could also see how a breaking change (such as one in the paths you are copying) could run into issues with your hardcoded approach.

    In the case of software like nginx, I would use the official image, mount config/cert files instead of copying, and extend in my own dockerfile if needed.