56
Do you rebuild your container images yourself? (lemmy.fromshado.ws)
submitted 10 months ago by to c/selfhosted@lemmy.world
20 comments fedilink hide all child comments
 

I'm talking not only about trusting the distribution chain but about the situation where some services dont rebuild their images using updated bases if they dont have a new release.

So per example if the particular service latest tag was a year ago they keep distributing it with a year old alpine base...

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

I'm also in this category, but OP is talking about something else.

Like if you use container-x, which has an alpine base. If it hasn't released a new version in several years then you're using a several year old alpine distro.

I didn't really realise this was a thing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 10 months ago (1 child)

    Ah, I have no idea what that is. I thought OP meant building stuff directly from Github (e.g. Ungoogled Chromium). Thanks for the clarification! :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 10 months ago

    Containers have layers. So if you create an instance of a syncthing container whoever built that container would have started with some other container. Alpine linux is a very popular base layer, just used as an example in this discussion.

    When you download an image, all the layers underlying the application that you actually wanted, will only be as fresh as the last time the maintainer built that image. So if there were a bug in the alpine base, that might have been fixed in alpine, but wouldn't by pushed through to whatever you downloaded.

  • permalink
  • fedilink
  • source
  • parent