-
Notifications
You must be signed in to change notification settings - Fork 327
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
can't initialize OpenStack storage driver in CoreOS #246
Comments
Great question. Going to have to do some research on this one. Worst case On Wednesday, January 6, 2016, scotthz [email protected] wrote:
|
@scotthz Have you found any more information related? I spent a few minutes but have not come up with a better answer so far. I wonder if |
@clintonskitson I looked briefly for another method to find openstack id but didn't find anything. Worked around it for now to meet my current need. Post-cloud-init, /bin, /sbin, /usr/bin, usr/sbin are all on a read-only filesystem in CoreOS. It occurred to me that they might be writeable during cloud-init. If so, it dmidecode could be written to usr/sbin when the VM is created. But that would probably break down when CoreOS updates itself. /etc is writeable, but rexray would know to look there in the event that it finds itself running on coreos or /usr/sbin/dmidecode doesn't exist. Or maybe the coreos people could add dmidecode to their distributions. |
Hi @clintonskitson, I have similar issue. Any workaround on this?
Thanks |
Thanks @clintonskitson, Allow changing bin file config is good, now, I've build rexray in container and it works |
@clintonskitson: Impossible for me to build ff03583, I get this error
Could you provide me with more details in order to get rid of this bug... I am not familiar with go compilation. I tried to follow build-reference but with no success. Thanks by advance |
It looks like you |
@clintonskitson You are right I was using a go version < 1.5 I just tried with go 1.6.1, but I stil get an error:
Thanks for your reply |
Closing due to inactivity. OpenStack can be revisited if new openstack driver is merged via https://github.com/codedellemc/libstorage/issues/182 |
When initializing the OpenStack storage driver, REX-Ray tries to execute /usr/sbin/dmidecode, which is not available in CoreOS. As a result,
CoreOS version:
Is there a more cloud-friendly way of getting the OpenStack instance id?
The text was updated successfully, but these errors were encountered: