HTTPS-Portal: Automated HTTPS server powered by Nginx, Let’s Encrypt and Docker

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by cm2187 on Friday September 14, 2018 @04:23AM (#17985580)

On 2, perhaps I misunderstood how docker works but don’t you need to deploy a docker image that is binary compatible with the type and version of the host OS? Then don’t you just move the problem? (Two customers with different types of OS require you to recreate the docker images). And what if these customers need to upgrade their version of linux, do they need to contact all their software vendors to reissue new docker images?

I never understood how creating the tight dependancy between the host and the docker image is not a problem.

[ Parent | on HN ]

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by SteveLTN on Friday September 14, 2018 @06:03AM (#17985998)

Well, you need to get a binary compatible docker image for the hardware. But frankly almost everyone uses x86-64 now, so this is not usually a problem. If these customer upgrade their version of Linux, the new Linux version usually comes with Docker, and you don't need to update the image.

[ Parent | on HN ]

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by cm2187 on Friday September 14, 2018 @07:14AM (#17986306)

ok so maybe I misunderstood. I thought the version of the host linux had to match exactly the version of the docker linux image.

[ Parent | on HN ]

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by pythonaut_16 on Friday September 14, 2018 @09:14AM (#17986946)

I believe the running containers share the host's kernel, so maybe if you were doing certain low level kernel level stuff, maybe the version of the kernel matching would matter?

[ Parent | on HN ]