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

One bad config is not ignored #216

Open
ghost opened this issue Mar 1, 2017 · 9 comments
Open

One bad config is not ignored #216

ghost opened this issue Mar 1, 2017 · 9 comments

Comments

@ghost
Copy link

ghost commented Mar 1, 2017

Use STORAGE_DRIVERS=overlay2 instead of correct STORAGE_DRIVER will result in some unexpected error messages.

# docker-storage-setup
ERROR: Invalid storage driver: devicemapper.

@rhvgoyal
Copy link
Collaborator

rhvgoyal commented Mar 1, 2017

Are you testing the latest code?

@rhvgoyal
Copy link
Collaborator

rhvgoyal commented Mar 1, 2017

I can't reproduce it.

@rhvgoyal
Copy link
Collaborator

rhvgoyal commented Mar 1, 2017

Oh you specified extra S, I can see it.

@rhvgoyal
Copy link
Collaborator

rhvgoyal commented Mar 1, 2017

Ok, this overrides that internal variable STORAG_DRIVERS and that's the problem.

@rhvgoyal
Copy link
Collaborator

rhvgoyal commented Mar 1, 2017

@rhatdan may be we should source the external files first and then define internal global variables to make sure users can't intentionally/accidentally override container-storage-setup gloabal variables?

@rhatdan
Copy link
Member

rhatdan commented Mar 1, 2017

#217

@rhvgoyal
Copy link
Collaborator

rhvgoyal commented Mar 1, 2017

@rhatdan I am playing with another patch where I want to initialize global variables after sourcing config file. That way all the globals will be protected.

@rhatdan
Copy link
Member

rhatdan commented Mar 1, 2017

We can also do that, but it could get confusing. We have globals that can be overridden, as well.

@rhvgoyal
Copy link
Collaborator

rhvgoyal commented Mar 1, 2017

I think I have taken care of that in my patch. Have a look.

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