-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kuryr-libnetwork fails on macOS #2
Comments
make run
fails when it executes ./stack.sh
with error message: error creating aufs mount to /var/lib/docker/aufs/mnt/61945c33665904d8446bd8fe8349ea7fba0858ebd7876bcbf68cdf7c0481a3
make run
fails when it executes ./stack.sh
with error message: error creating aufs mount to /var/lib/docker/aufs/mnt/...
make run
fails when it executes ./stack.sh
with error message: error creating aufs mount to /var/lib/docker/aufs/mnt/...
make run
fails when it executes ./stack.sh
with: error creating aufs mount to /var/lib/docker/aufs/mnt/...
make run
fails when it executes ./stack.sh
with: error creating aufs mount to /var/lib/docker/aufs/mnt/...
Indeed dockerlint is broken, I created a separate issue #3. From your log I suspect you are using macOS? Docker privileged mode might not be fully supported, that's why the kuryr setup fails. I don't own a Mac so I cannot verify that. You could try to exclude the following projects from Dockerfile and local.conf
|
Thanks, it is a MacOS High Sierra that I have. I tried your suggestion and at first glance, it appears to be successful. This is the output of my
Is it not authorized because zun installation has been excluded? Adding a debug tag results in the following:
The reason this is interesting is because when I log into horizon dashboard and try to create a new container, it is stuck on Perhaps I should give up trying to make this work from within a docker container as it is clearly not the intended use case. I should install this on an Ubuntu installation rather than trying to make it work inside a docker container which I assumed was able to replicate the same processes across platforms and that assumption clearly appears to be wrong! |
As you excluded Zun (the container management plugin), that's not surprising. However, you should be able to create regular compute nodes (VMs) and anything else inside your DockStack. To be fair, I never stated platform portability was a goal of this project. In fact, I list a recent Ubuntu as requirement. Even without DockStack, getting an Ubuntu machine is a good idea–as recommended in the OpenStack development docs. Good luck! |
I get past
make build
okay but the setup fails when I domake run
.Please look at my installation log.
Also the content of worlddump-2018-02-09-164954.txt mentioned in the final lines of installation log above.
So
make lint
seem to be broken too but that is perhaps a minor issue here.The text was updated successfully, but these errors were encountered: