Hi jay vyas
Thanks for trying, it looks like the patch doesn't general enough.
Maybe we can refine the patch better by resolve issues you encountered.
I see you have a vagrantfile and using docker as the provider , if thats the case, why not have vagrant also do the docker build as well using ? just curious, no big deal.
You're right! but I got following error message by doing so...
Cachier plugin only supported with docker provider when image is used
And since the images building is a one time effort, so I separate it out. Once we have cachier plugin supported, maybe we can make it easier as you suggested.
I had to run everything as sudo. that could be a docker mistake im maknig. Is that supposed to be a requirement? otherwise it cant see /var/docker/run
Ok, would you mind to describe your environment and what command require you to run as sudo?
I test it on a centos 6.5 VM running everything as root, so it could be a missing puzzle I did not take care of it.
It seems like it was blocked. so i went ahead and added a nohup to the RUN ssh -d in the Dockerfile and added another command after
Sounds like the docker build is blocked? I'd like to figure out what happened. Could you describe me the scenario like where you got blocked?
Right now, it seems to hang. rebooted, now getting some kind of port conflict?
I'm guessing that might due to the vagrant provisioning isn't going well so containers are broken and still running there. If the provisioning failed, sometimes it require to manually destroy containers by using the docker command.
Anyhow, thank you so much for the feedback. I'll test it on a non-root scenario first and see what's going on.