Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Using the --init flag #81
@crosbymichael Thanks for the reply.
For example, since tini 0.13.0 is the init shipped with docker today, and I say I add tini 0.10.0 and want to point to that? Because when I tried this today, that feature did not appear to work to change which version tini it ran. It was always 0.13.0 (I realize that if this is indeed a problem, it belongs on the docker issues, I'm just trying to understand how to use tini with all these new features :) )
FROM alpine RUN apk add --update tini
@andyneff One of the Docker folks (@crosbymichael or @tianon) would be able to confirm, but I believe the
Now, to answer your initial questions:
I think it depends on who's going to use your image.
If your image is meant to be used by other people (e.g. you push it to the Docker Hub, or expect people to clone your repo and build it, etc.), then you probably want to include Tini in your image and use it as the
Tini can be chained with itself without any issue, so if you embed it and someone also uses the
All that being said, if your image is something you're only using for yourself (or your organization), and you always run your containers on a recent version of Docker using the
Should be answered above
One caveat though: that's just my opinion; @crosbymichael, who worked on the feature on the Docker side, may have a better claim at providing the "preferred" method!