NavigationContentFooter
Jump toSuggest an edit

Compatibility between OS Images and different Flexible IP type combinations

Reviewed on 09 September 2024Published on 09 September 2024

This page presents the currently known state of compatibility between Scaleway Instance OS Images and the different combinations of Flexible IPs types.

Configuration

routed_ipv4routed_ipv6
1v4-0v610
Nv4-0v62+0
0v4-1v601
0v4-Nv602+
1v4-1v611
Nv4-Nv62+2+

Matrix

Image label1build_date2build_tag31v4-0v6Nv4-0v60v4-1v60v4-Nv61v4-1v6Nv4-Nv6
almalinux_820240703154090041a7b⚠️4⚠️4
almalinux_9202407041520a0e9a547⚠️4⚠️4
centos_stream_92024070907049d844f31⚠️4⚠️4
rockylinux_8202407031543e583b9f3⚠️4⚠️4
rockylinux_92024070315008e17111b⚠️4⚠️466
fedora_39202408261203db379337⚠️4⚠️477
fedora_402024082315292e2324a6⚠️4⚠️466
debian_bullseye20240823151020ada37d⚠️4⚠️5
debian_bookworm202408231520ff285693
ubuntu_focal202409021112b2eb59c9
ubuntu_jammy2024070315381afe725f
ubuntu_noble202407031541a6b4f635

Callouts

  • 1 - Image label as presented be the Marketplace API
  • 2 - The value of the build_date field in the /etc/cloud/scw-build.info file
  • 3 - The value of the build_tag field in the /etc/cloud/scw-build.info file
  • 4 - Instance is reachable but the DNS resolution is not working
  • 5 - Same as 4 + only the first IPv6 gets configured automatically
  • 6 - The Flexible IP attachment order matters: this only works if at least one routed_ipv6  is attached to the Instance after at least one routed_ipv4 has been attached
  • 7 - The version of cloud-init is too old to support such a configuration
Docs APIScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCarreer
© 2023-2024 – Scaleway