Compatibility between OS Images and different Flexible IP type combinations
This page presents the currently known state of compatibility between Scaleway Instance OS Images and the different combinations of Flexible IPs types.
Configuration
routed_ipv4 | routed_ipv6 | |
---|---|---|
1v4-0v6 | 1 | 0 |
Nv4-0v6 | 2+ | 0 |
0v4-1v6 | 0 | 1 |
0v4-Nv6 | 0 | 2+ |
1v4-1v6 | 1 | 1 |
Nv4-Nv6 | 2+ | 2+ |
Matrix
Image label1 | build_date2 | build_tag3 | 1v4-0v6 | Nv4-0v6 | 0v4-1v6 | 0v4-Nv6 | 1v4-1v6 | Nv4-Nv6 |
---|---|---|---|---|---|---|---|---|
almalinux_8 | 202407031540 | 90041a7b | Yes | Yes | Partly4 | Partly4 | Yes | Yes |
almalinux_9 | 202407041520 | a0e9a547 | Yes | Yes | Partly4 | Partly4 | Yes | Yes |
centos_stream_9 | 202407090704 | 9d844f31 | Yes | Yes | Partly4 | Partly4 | Yes | Yes |
rockylinux_8 | 202407031543 | e583b9f3 | Yes | Yes | Partly4 | Partly4 | Yes | Yes |
rockylinux_9 | 202407031500 | 8e17111b | Yes | Yes | Partly4 | Partly4 | Yes 6 | Yes6 |
fedora_39 | 202408261203 | db379337 | Yes | Yes | Partly4 | Partly4 | No7 | No7 |
fedora_40 | 202408231529 | 2e2324a6 | Yes | Yes | Partly4 | Partly4 | Yes6 | Yes6 |
fedora_41 | 202410311306 | 67e3f2fd | Yes | Yes | Partly4 | Partly4 | Yes6 | Yes6 |
debian_bullseye | 202408231510 | 20ada37d | Yes | Yes | Partly4 | Partly5 | Yes | Yes |
debian_bookworm | 202408231520 | ff285693 | Yes | Yes | Yes | Yes | Yes | Yes |
ubuntu_focal | 202409021112 | b2eb59c9 | Yes | Yes | Yes | Yes | Yes | Yes |
ubuntu_jammy | 202407031538 | 1afe725f | Yes | Yes | Yes | Yes | Yes | Yes |
ubuntu_noble | 202407031541 | a6b4f635 | Yes | Yes | Yes | Yes | Yes | Yes |
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
Still need help?Create a support ticket