Related

Tool DOCTL: DigitalOcean CLI Tool
Can I assign a firewall while creating a droplet via API? Question Question
token url in google smart home action authantication Question Question

Question

Unable to retrieve Kernel details via API

Posted September 26, 2016 1.6k views
APICoreOS

I started a couple of days ago with DO and now I have an issue with the API. According to the API docs is it possible to retrieve details about the kernel. Both my droplets return null with a working READ/WRITE token.

$ curl -X GET  -H "Authorization: Bearer $TOKEN" "https://api.digitalocean.com/v2/droplets/25333333"
{  
   "droplet":{  
...
      "status":"active",
      "kernel":null,
      "created_at":"2016-09-11T11:17:02Z",
...

Am I missing something?

Add a comment
fabianaffolter
By:
fabianaffolter

Related

Tool DOCTL: DigitalOcean CLI Tool
Can I assign a firewall while creating a droplet via API? Question Question
token url in google smart home action authantication Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers
asb September 26, 2016

Newer DigitalOcean Droplets use their own bootloaders and “internally managed” kernels. For these Droplets, the API will report the "kernel" as null as you can not change the kernel either through the API or the control panel. You can update or install new kernels as you normally would on a bare-metal server. We can probably make that more clear in the API documentation.

We’ve also provided an upgrade path for older Droplets. In order to use the “internally managed” kernels without rebuilding your Droplet, you can now set the “DigitalOcean GrubLoader” from your Droplet’s kernel menu or via the API.

Find more details here:

https://www.digitalocean.com/community/tutorials/how-to-update-a-digitalocean-server-s-kernel

Reply Report
fabianaffolter September 27, 2016

Thanks for your response.

Why not display the current kernel even if it’s an “internally managed” kernel? Showing what kernel is in use and not allow to change it through the API are two different topics from my point of view.

No need to login and to use uname ;-)

Reply Report

Related

Looking for something else?

Ask a new question Search for more help