Introducing Scaleway NextGen NVMe Cloud Servers with Hot-Snapshots. 🚀


Community tutorials and documentations

Enable or disable localboot for virtual cloud servers

Local boot option on virtual Cloud servers

This page shows you how to switch between the local boot and the bootscript option on a virtual cloud server.


  • You have an account and are logged into
  • You have configured your SSH Key
  • You have a virtual cloud server

Scaleway virtual cloud servers are now using the local boot option by default, instead of by using a Bootscript.

Kernels and Initrd are installed directly on the volume, which allows you to use the distribution kernel or any customized kernel of your choice.

To switch to local boot, you will need to re-create your server with one of our new local boot compatible images.
All newly created x86 Cloud Servers will use a local kernel by default. Previously created servers do not support local boot and can’t use this feature!

Bootscripts are still available, for example, to boot your server into rescue mode to debug your server.

How to switch the boot option

Note: Local boot is currently available for all our x86_64 based virtual cloud servers. It will become available for our ARM64 virtual cloud server in a few days.

Important: Local boot is only available for virtual cloud servers. It is not possible to use it with BareMetal instances, as the volume is not accessible during the boot process.

To switch between the local boot and bootscript options, go to the status page of your server and click on the Show button in the Advanced section:

Show the advanced section

Enable local boot

To enable the local boot option, move the Local Boot slider to ON :

Enable local boot

Disable local boot

To disable the local boot option and to boot your server by using a bootscript, move the Local Boot slider to OFF.

The bootscript option will become visible, and you can choose the bootscript that you want to use:

Disable local boot

To boot your server into rescue mode in case you need to debug your server, choose the rescue bootscript from the list of available bootscripts and reboot your server from the management console.

Important: If you use CentOS or Fedora and doesn’t disable SELinux on the instance from within rescue, your instance will not reboot successfully because SELinux labels will be corrupted.

Discover a New Cloud Experience

Deploy SSD Cloud Servers in seconds.