How I manage my Containers and their Vulnerability Management across selfhosted infrastructure and how the patching of PHP2SHELL looked like

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 2 days ago (3 children)

Why not use PHP hardened (distroless) images as a base for the final image?

Why build your own images at all? I'm not sure I understood what advantage that gives you.

Harbor looks interesting but that install procedure is ridiculous. Why would I run an installer script just to pull docker images, just give me a compose file ffs. The only way I'd ever consider it is inside an LXC container or a VM.

Also, it sounds like they've never heard of a reverse proxy and don't know you can do TLS that way? That does not inspire confidence.

  • source
  • hideshow 3 child comments
  • [–] 8 points 2 days ago (1 child)

    Why build your own images at all?

    Trust. A LOT of docker images are just some person who decided to do it first. Hopefully php has an official one though.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 5 points 2 days ago*

    PHP hardened (distroless) images

    That's a good point, maybe I'll change that at some point. The reason, haven't done so yet is that I wanna have the whole supply chain under my control. And know exactly what has been changed since a release.

    Why build your own images at all?

    Because of different reasons:

    • Flexibility: I can modify a container to my needs.
    • Trust: I don't wanna rely on something that I don't have under control. An image might contain some breaking changes in the next version, and that could cause me problems when I apply them.
    • Learning: By doing everything myself I learn about how to do it.
  • source
  • parent