@mrmason i'll have more to share soon, sorry about the delay Tom
Great tool, guys!
I just need a pointer on my output.
My image contains custom headless chrome(CEF), docker-slim minifies it well, but I run my container it crashes after sometime when I access my container with the following error:
[0100/000000.789662:ERROR:zygote_linux.cc(614)] Zygote could not fork: process_type renderer numfds 5 child_pid -1
[0100/000000.791877:ERROR:zygote_linux.cc(646)] write: Broken pipe (32)
/opt/distrib/init.sh: line 10: 10 Trace/breakpoint trap (core dumped) $PWD/my_browser --no-sandbox --disable-gpu --disable-gpu-compositing
my build cmd:
sudo ./docker-slim build --include-path=/tmp --include-path=/opt/distrib --include-bin=/bin/busybox --tag abc-slim:v1 --http-probe=false abc-fat:v1
sudo ./docker-slim build --include-path=/tmp --include-path=/opt/distrib --include-bin=/bin/busybox --tag abc-slim:v1 --http-probe=false abc-fat:v1
It seems the chrome couldn't create the forks
@malys great to hear it works with your on prem Gitlab environment! got a chance to test it only with the standard Gitlab CI setup and that environment requires a bit of work to configure the DOCKER_HOST environment variable properly (i added the instructions to the readme, just in case)
@srikantpatnaik Also curious what you are doing with /dev/snd in your container
How to pass environment variable to docker-slim using --env flag?
We are evaluating docker-slim with our containers and hope to add it to our CI/CD pipeline in case its successful.
The question I have is, how to pass arguments to docker-slim command that is required to start the container. From my understanding, docker-slim brings up the docker image, runs a probe to understands how to minimize. When it does try to start the container, certain arguments are required for the container to startup and it would be great if one of you could shed light on it.
The question I have is, how to pass arguments to docker-slim command that is required to start the container. From my understanding, docker-slim brings up the docker image, runs a probe to understands how to minimize. When it does try to start the container, certain arguments are required for the container to startup and it would be great if one of you could shed light on it.
@kcq
"--env" is similar to the "-e" option
you can also specify a custom network to use with the "--network" flag
or a custom link with "--link"
you can set the working directory with the "--workdir" flag
you can also expose ports (in case you don't have the EXPOSE instructions in your Dockerfile) with the "--expose" flag
"--hostname" can be used to set the hostname for the temporary container
if you want to add records to /etc/hosts you can use the "--etc-hosts-map" flag
there's also "--container-dns" and "--container-dns-search" for the dns related configurations
docker-slim build always fails with any of the Go samples untouched. Fwiw, it also fails with my own container ;-)
info=container status=created name=dockerslimk_51426_20191211150105 id=585c79c09a5481a7967948391876a49f67e251f6ee19e618f72ab0fa6e649f01
docker-slim[build]: info=container status=crashed id=585c79c09a5481a7967948391876a49f67e251f6ee19e618f72ab0fa6e649f01
docker-slim: container stdout:
docker-slim: container stderr:
standard_init_linux.go:211: exec user process caused "exec format error"I'm on OSX (10.13.6 (17G10021)) with Docker 19.03.5.
Any idea?
when i use docker build ,it is ok
but i use docker-slim,request to http://registry.weihong.com.cn/minimist failed, reason: getaddrinfo ENOTFOUND registry.weihong.com.cn registry.weihong.com.cn:80
no found registry.weihong.com.cn
what i can do?
I use --include-path, but it no work
i'm using java, mvn, gradle, node and python beneath oracle linux as a base image, all built in into a one docker image that has around 2 gb of size.. no http-probes and no port exports..
tried to fire docker-slim into that image but it gave around 3 mb image that has a nothing inside.
@jasperamorgan_gitlab has similar issue of the one I have..
my point is how to get the 2gb image smaller and faster with docker-slim.
tried to fire docker-slim into that image but it gave around 3 mb image that has a nothing inside.
@jasperamorgan_gitlab has similar issue of the one I have..
my point is how to get the 2gb image smaller and faster with docker-slim.
Hey everyone. I'm trying to run docker-slim from within docker (using the image from docker hub, dslim/docker-slim), but I'm running into issues: docker-slim can't seem to perform its HTTP probes because the connections are being refused. When running the exact same docker-slim build command on the host, everything works fine. Am I overlooking some crucial flag I should be using when running docker-slim from within docker?
https://gist.github.com/otaconix/397ff08558c098631b73499472bd7391 This gist should contain all that's necessary to reproduce my issue
@delabassee_twitter sorry for the headaches! I wonder where you installed docker-slim on your Mac... What's the directory name? Can you also run
file docker-slim-sensor in that directory to see the system architecture for the sensor executable. Can you also share the output when you run docker-slim version?
@ZhouBox I assume
registry.weihong.com.cn is referenced in your Dockerfile somehow, right? If this is the case it's a gap in functionality right now... The --etc-hosts-map value is only applied at runtime when the image is minified (it's not used when the image is build like it would happen with docker build --add-host. I'll open a Github issue to track this enhancement. Thank you for sharing your use case!
@ZhouBox Can you share the full
docker-slim command line when you are trying to use the --include-path parameter? It'll help reproducing the condition.
@mr.docker_gitlab are you trying to minify a base image or do you have your application (or a set of applications) in that image? What's the purpose/function of that image? Minifying base images with
docker-slim is technically possible, but it requires extra effort and you need to use the --include-* params like --include-path, --include-bin and --include-exe parameters for docker-slim to specify explicitly what you want to keep. There's a future enhancement that will help with minifying base images (ability to minify images specifying multiple command line applications you want to keep). I'll be happy to ping you when it's available and it'll be super if you have cycles to work on this feature if you'd like to see it sooner :)