Hi Olaf, This is difficult to debug: "Write failed: Broken pipe"
I bet it must been caused by SELINUX. Please make SELINUX has been disabled before running docker. Although Jay helped to add this note in our README: https://github.com/apache/bigtop/blob/master/bigtop-deploy/vm/vagrant-puppet-docker/README.md#getting-started But since the error message is too meaningless, I think we can implement a simple check to get SELINUX status on host machine and exit the deployment if it is not disabled. 2015-03-18 7:40 GMT+08:00 Konstantin Boudnik <[email protected]>: > That's weird - I believe it worked ok for me last time I've tried it a few > weeks back. And I think I was on Ubuntu 14.04 > > Sorry, I know it doesn't help much :( > > On Wed, Mar 18, 2015 at 12:06AM, Olaf Flebbe wrote: > > Hi, > > > > Since I am struggling with getting the vagrant-puppet-docker things to > run correct on debian, I now tried to use the centos6 way. > > > > image: Removing intermediate container 05e60389c4c4 > > image: Step 10 : CMD /usr/sbin/sshd -D > > image: ---> Running in eea418d398ea > > image: ---> bb7b742d718d > > image: Removing intermediate container eea418d398ea > > image: Successfully built bb7b742d718d > > image: > > image: Image: bb7b742d718d > > ==> image: Creating the container... > > image: Name: vagrant-puppet-docker_image_1426631760 > > image: Image: bb7b742d718d > > image: Volume: > /home/olaf/bigtop/bigtop-deploy/vm/vagrant-puppet-docker:/vagrant > > image: > > image: Container created: 3ad3a952ffc098a6 > > ==> image: Starting container... > > ==> image: Provisioners will not be run since container doesn't support > SSH. > > Pseudo-terminal will not be allocated because stdin is not a terminal. > > Write failed: Broken pipe > > > > Just wondering how it is suppose to work at all. > > > > Olaf > > >
