dockerfiles
dockerfiles copied to clipboard
SvenDowideit
dockerfiles that I use
Hi, Can you add an inspect on Mounts section in 'setup-samba-share.sh' : ``` volumes=`$DOCKER inspect --format='{{range \$k,\$v := .Config.Volumes}}{{println \$k}}{{end}}' "$container" | grep -v -E "^$" $DOCKER inspect --format='{{range \$k,\$v...
This fixes issues #29 and #17. But it also breaks compatibility. I pushed it to [niccokunzmann/samba-share](https://hub.docker.com/r/niccokunzmann/samba-share/). - Do you want to maintain it? - Do you want to merge it?...
docker inspect from Volume Containers using docker 1.8 are returning volumes in .Config.Volumes. Made a change to search both ways
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: ``` please...
Is there a version of this you can turn the UDP flag on? We need to be able to use this for DNS and dig across bastions.
Not sure if this rates as a samba, docker, or ubuntu issue, but: ``` # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2c93025ecbcf ubuntu:latest /bin/bash 11 seconds...
besides issue #47 reported that the "-D info" no longer outputs "Init Path", envsubst fails also using the env variables (USER,GROUP .. ) to create smb.conf. workaround: ``` FROM svendowideit/samba...
The https://github.com/SvenDowideit/dockerfiles/blob/master/samba/setup.sh entrypoint script expects to find "Init Path" in the docker info output, but that no longer appear to be output. I'm working around it by modifying the script...
