My Instance is attached to a Private Network but autoconfiguration is not working

Default Instance images for Ubuntu, Debian and CentOS support autoconfiguration of interfaces plugged into a Private Network.

They leverage helper scripts provided by the scaleway-ecosystem package. These scripts:

• enable DHCP on the interfaces plugged into a Private Network
• when Instances are attached to Private Networks plugged into Public Gateways, make the default route received by DHCP the primary route for all traffic on the Instance
• keep the route to the Scaleway Metadata API more specific (see below).

If your Instance does not get autoconfigured, it may be that you are using an old version of the scaleway-ecosystem package. scaleway-ecosystem 0.0.4 or later is required. Use the following command to update it:

• On Ubuntu (Focal and Jammy) or Debian (Stretch and Buster):

  add-apt-repository ppa:scaleway/stable && apt update && apt install scaleway-ecosystem
  add-apt-repository ppa:scaleway/stable && apt update && apt install scaleway-ecosystem
  apt list scaleway-ecosystemCopy

• On Debian distributions (Bookwork, Bullseye and Buster):

  cat << EOF > /etc/apt/sources.list.d/scaleway-ubuntu-debian-stable-jammy.list
  deb http://ppa.launchpad.net/scaleway/debian-stable/ubuntu jammy main
  # deb-src http://ppa.launchpad.net/scaleway/debian-stable/ubuntu jammy main
  EOF
  apt -y update
  apt install scaleway-ecosystem
  apt list scaleway-ecosystemCopy

• On CentOS 7:

  yum -y install yum-plugin-copr
  yum -y copr enable @scaleway/instances
  yum -y install scaleway-ecosystemCopy

• On Centos Stream 8 and later, RockyLinux, AlmaLinux or Fedora:

  dnf -y copr enable @scaleway/ecosystem
  dnf -y install scaleway-ecosystemCopy