i just ended up going with a new image with the components installed, which i’ve been informed is best practice.

  • aksdb@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 month ago

    The idiomatic way would be to build your own image. That’s exactly the strength of the layering of container images.

    • Nico198XOP
      link
      fedilink
      arrow-up
      1
      ·
      30 days ago

      understood. this is the route i ended up taking. thank you!

      • aksdb@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        29 days ago

        I think you won’t regret it. If the container startup installs stuff, you might lock yourself out when the remote server has issues, your network has issues, or if the package you install changes due to an update.

        With it baked into an image, you have reproducible results. If you build a new image and it doesn’t work anymore, you can immediately switch back to the old one and figure out the issue without pressure.

        • Nico198XOP
          link
          fedilink
          arrow-up
          2
          ·
          29 days ago

          great thoughts, thank you for sharing! i’m still quite new to containerization.