Skip to content
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

OSX: blockade.yml doesn't work, blockade.yaml does #43

Closed
kklocek opened this issue Nov 15, 2016 · 1 comment
Closed

OSX: blockade.yml doesn't work, blockade.yaml does #43

kklocek opened this issue Nov 15, 2016 · 1 comment

Comments

@kklocek
Copy link
Contributor

kklocek commented Nov 15, 2016

Hello!

I read blockade guide, however I was stuck on creating blockade.yml file. When I save it and run blockade up in response I got:
NODE CONTAINER ID STATUS IP NETWORK PARTITION

However if I changed file name to blockade.yaml it works fine.

I have a fix to docs (just one character...) but is it not an internal issue?

I used blockade file from ==> http://blockade.readthedocs.io/en/latest/guide.html
OS: macOS Sierra 10.12.1
Docker version:
Version 1.12.3 (13776)
Channel: Stable
583d1b8ffe

@labisso
Copy link
Member

labisso commented Nov 16, 2016

Yes you are right. this is a bug introduced in a recent refactor. Either yaml or yml extension are supposed to work. I'll fix it soon but merge your doc PR first to avoid other people having the same confusion. Thanks!

@labisso labisso closed this as completed in 322e2ac Dec 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants