Hi, Thanks for getting back to me.
As for sharing the setup - I have cut the files down to the minimum needed to show the problem and popped them onto github, https://github.com/psl-trifork/riak-docker The actual project is a lot more complicated but this one riak docker image is proving to be a pain when run on Windows and only Windows. Linux and MacOS are fine. If you can spot any obvious gotchas then please do let me know. Thanks in advance. ——————————————————————————— Pete Slater Trifork Leeds Ltd, Round Foundry Media Centre, Foundry Street, Leeds LS11 5QP, UK Skype ID: psl.trifork E-Mail: [email protected]<mailto:[email protected]> www: www.trifork.com<http://www.trifork.com> On 31 Aug 2015, at 19:38, Christopher Mancini <[email protected]<mailto:[email protected]>> wrote: Hey Pete, If you want to share your setup, I will try to replicate the problem and see if I can help. Chris On Mon, Aug 31, 2015 at 2:08 PM Matthew Brender <[email protected]<mailto:[email protected]>> wrote: Hey Pete, That's an interesting situation that leads me to think its a Windows Vagrant consideration, given that everything runs on OS X. Is your Dockerfile in a place we could see it and/or run it? FWIW, Hector has a project that works well. Maybe you can reference his setup [0]. I'd also welcome a cross-post to StackOverflow in case its a common Windows + Vagrant issue that our community may miss [1]. [0] http://stackoverflow.com/questions/tagged/riak [1] https://github.com/hectcastro/vagrant-multi-docker-riak Matt Brender | Developer Advocacy Lead Basho Technologies t: @mjbrender On Fri, Aug 28, 2015 at 3:49 AM, Pete Slater <[email protected]<mailto:[email protected]>> wrote: > > I am having a problem with a Docker image running Riak which is causing me > concern. > > I have a Docker image which is being run inside of a Vagrant container. The > Docker image is running Riak in a CentOS 7 guest OS and is configured to > start via a supervisor script. > > The issue I am having is that when running the Vagrant VM in a MacOS host OS, > Riak in the Docker image starts fine. > > However when I run the same Vagrantfile in a Windows host OS, Riak fails to > start with an error ‘Protocol: ~tp: the name > [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> > seems to be in use by another erlang node’ > > I have tried changing the codename but the error persists. > > The strange thing is that Riak seems to be running as we can query it via the > REST API. But when trying to communicate to it when logged into the Docker > container and doing something like ‘riak ping’ we get Node > ‘[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>’ > not responding to pings. > > Any help would be appreciated. If you need further information then please > ask. > > > > > > > _______________________________________________ > riak-users mailing list > [email protected]<mailto:[email protected]> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list [email protected]<mailto:[email protected]> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
