Closed alifiroozi80 closed 1 year ago
Is test:1.0.0
in your experiment a base image that includes the tini
binary or is it an application image that happens to include tini
too? What is in your Dockerfile? What is it doing?
There's a way to keep extra files and directories using one of the --include-*
filags. For example, --include-path
is used to keep a file a directory in your image even if it's not used during minification. You can use. this flag to keep libc though you'll need to have extra --include-path
flags to include the symlinks for libc too.
Hello guys,
I have
Dockerfile,
which usestini
for process handling.Everything is okay if I build the image as usual (
docker build -t test:1.0.0 .
).But if I use slim to slim the image and run the newly slimmed Image, it returns:
Its documentation says:
So, slim delete this dependency.
How can I keep the
libc
dependencies after sliming?