Open edenisn opened 7 years ago
This is due to newer versions of the Docker binary being no longer statically linked. You can possibly fix this by runningRUN curl -sSL https://get.docker.com/ | sh
in the Dockerfile - this should grab the latest version of the docker binary inside the temp build container and satisfy all deps. Good luck - that still didn't get the container to work for me.
argh. this is really painful - I wonder if they're still building a static client.
There are a number of other issues with the container which sadly made me abandon my attempts to revive it and switch over to a more traditional page full of -e and -v Samba container. I really love the approach you took to this, and hope someone can take the time to dust it off.
I run data container:
docker run -v /data --name my-data busybox true
then run:docker run --rm -v $(which docker):/docker -v /var/run/docker.sock:/docker.sock svendowideit/samba my-data
and get the error: