properly check if docker is usable for $USER
Bug #1473554 reported by
Harm Weites
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Low
|
Unassigned |
Bug Description
Introduce a proper check on usability of docker and bail if it's not usable. The current behavior is to 'just read the docs!', which not everybody does, and inflict mayhem if $USER tries to do anything docker. Not good.
Changed in kolla: | |
assignee: | nobody → Swapnil Kulkarni (coolsvap) |
Changed in kolla: | |
importance: | Undecided → Low |
milestone: | none → liberty-2 |
Changed in kolla: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Yes, don't just do a group membership test. Perhaps checking the return value of "docker info" may work, but in the case of the docker client not being installed (such as inside an atomic container), checking the permissions of the socket file in the default location I would think is the best approach.