-
Notifications
You must be signed in to change notification settings - Fork 15
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
Cannot specify image_guid #59
Comments
This should only kick up if https://github.com/audiolize/vagrant-softlayer/blob/master/lib/vagrant-softlayer/config.rb#L258-L259 Reference the Load Order and Merging at the end of the Quck Start guide. |
Well, the image I created I fired up from their CentOS 5 image and immediately created an image from it (as a test). I included the default 25GB drive in it. My .box contains one file only (metadata.json) and its contents are below.
|
Does your box include its own |
Also, I found that I had to explicitly unset the competing parameters. Even though I did not set a OS value in the Vagrantfile with sl.operating_system, because I used some other services like winrm, the value was getting set for me. In addition to setting the image_guid parameter, I explicitly set operating_system to nil. Then it worked. |
Thats odd and that to me would definitely be a bug somewhere, when we initialize them its set to |
nil worked! Cool, thanks for the tip lonniev! (provider.operating_system = nil) I had previously tried "" as I noticed it seemed to be defaulting to "UBUNTU_LATEST" but I guess one needs to be more explicit than that. I would say that this is a bug as you shouldn't need to set OS to nil if you are setting the image_guid. Thanks all. |
same problem here. Thanks! |
It seems when I try to specify a custom image, I get this error:
I am not specifying an OS in my Vagrantfile. When I comment out my image_guid, and use an OS name instead, it works fine. I got the image GUID from the SL CLI tool. A small excerpt from my VagrantFile is below, let me know if it is too small.
The text was updated successfully, but these errors were encountered: