scaleway / packer-plugin-scaleway Goto Github PK
View Code? Open in Web Editor NEWPacker plugin for Scaleway Builder
Home Page: https://www.packer.io/docs/builders/scaleway
License: Mozilla Public License 2.0
Packer plugin for Scaleway Builder
Home Page: https://www.packer.io/docs/builders/scaleway
License: Mozilla Public License 2.0
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Add attributes to create or import block volumes when starting build instance
source "scaleway" "basic" {
commercial_type = "DEV1-S"
image = "ubuntu_jammy"
image_name = "image-name"
ssh_username = "root"
zone = "fr-par-1"
remove_volume = true
block_volumes {
name = optional_or_generated
size = 20
}
block_volumes {
name = optional_or_generated
snapshot_id = xxxx-xxxx-xxxx-xxxx
}
}
block_volumes would be deleted if using remove_volume
option
To fix beforehand: #86
To properly make an image to be booted by new machines, data specific to a specific boot needs to be deleted, or recreated at the next boot. One such example is SSH hosts keys: they will be generated by the packer boot then stored in the image, hence all instances created from this image will share the same SSH host keys. Another example is the DUID used by DHCP clients; while it is not an issue for the public interface, it is an issue for the DHCP provided by the VPC Public Gateway: all instances spawned from the same image will get the same IP address.
Latest
{
"type": "scaleway",
"project_id": "YOUR PROJECT ID",
"access_key": "YOUR ACCESS KEY",
"secret_key": "YOUR SECRET KEY",
"image": "ubuntu_focal",
"zone": "fr-par-1",
"commercial_type": "DEV1-S",
"ssh_username": "root",
"ssh_private_key_file": "~/.ssh/id_rsa"
}
For most of the data mentioned here, this is controlled by the /etc/machine-id
file, which needs to be cleared at the end of the build process. This will make systemd
consider the next boot as the first boot of the machine, effectively regenerating all data specific to the machine:
The best solution would be for the plugin to add an extra step, after all the user steps and before the machine shutdown, that would:
/etc/machine-id
(NOT delete it, only clear it)Thanks!
Got strange error about api timeout even if it seems to work when using curl
packer build build_scaleway.pkr.hcl
1.8.3
Using the provided exemple in this repo build_scaleway.pkr.hcl
MacOSX M1-pro Monterey
packer installed through asdf
packer build build_scaleway.pkr.hcl
2022/09/26 18:10:58 [INFO] Packer version: 1.8.3 [go1.17.11 darwin arm64]
2022/09/26 18:10:58 Old default config directory found: /Users/frederic/.packer.d
2022/09/26 18:10:58 [TRACE] discovering plugins in /Users/frederic/.asdf/installs/packer/1.8.3/bin
2022/09/26 18:10:58 Old default config directory found: /Users/frederic/.packer.d
2022/09/26 18:10:58 [TRACE] discovering plugins in /Users/frederic/.packer.d/plugins
2022/09/26 18:10:58 [DEBUG] Discovered plugin: scaleway = /Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64
2022/09/26 18:10:58 [INFO] found external [-packer-default-plugin-name-] builders from scaleway plugin
2022/09/26 18:10:58 [TRACE] discovering plugins in .
2022/09/26 18:10:58 [INFO] PACKER_CONFIG env var not set; checking the default config file path
2022/09/26 18:10:58 [INFO] PACKER_CONFIG env var set; attempting to open config file: /Users/frederic/.packerconfig
2022/09/26 18:10:58 [WARN] Config file doesn't exist: /Users/frederic/.packerconfig
2022/09/26 18:10:58 Old default config directory found: /Users/frederic/.packer.d
2022/09/26 18:10:58 [INFO] Setting cache directory: /Users/frederic/.cache/packer
2022/09/26 18:10:58 Old default config directory found: /Users/frederic/.packer.d
2022/09/26 18:10:58 [TRACE] listing potential installations for "github.com/scaleway/scaleway" that match ">= 1.0.5". plugingetter.ListInstallationsOptions{FromFolders:[]string{"/Users/frederic/.asdf/installs/packer/1.8.3/bin/packer", ".", "/Users/frederic/.packer.d/plugins"}, BinaryInstallationOptions:plugingetter.BinaryInstallationOptions{APIVersionMajor:"5", APIVersionMinor:"0", OS:"darwin", ARCH:"arm64", Ext:"", Checksummers:[]plugingetter.Checksummer{plugingetter.Checksummer{Type:"sha256", Hash:(*sha256.digest)(0x14000084100)}}}}
2022/09/26 18:10:58 [TRACE] Found the following "github.com/scaleway/scaleway" installations: [{/Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 v1.0.6}]
2022/09/26 18:10:58 [INFO] found external [-packer-default-plugin-name-] builders from scaleway plugin
2022/09/26 18:10:58 [TRACE] Starting external plugin /Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 start builder -packer-default-plugin-name-
2022/09/26 18:10:58 Starting plugin: /Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 []string{"/Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64", "start", "builder", "-packer-default-plugin-name-"}
2022/09/26 18:10:58 Waiting for RPC address for: /Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64
2022/09/26 18:10:58 Received unix RPC address for /Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64: addr is /var/folders/n_/jtqch7ls28534bbt4hl905mr0000gn/T/packer-plugin2006929771
2022/09/26 18:10:58 packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 plugin: 2022/09/26 18:10:58 Plugin address: unix /var/folders/n_/jtqch7ls28534bbt4hl905mr0000gn/T/packer-plugin2006929771
2022/09/26 18:10:58 packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 plugin: 2022/09/26 18:10:58 Waiting for connection...
2022/09/26 18:10:58 packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 plugin: 2022/09/26 18:10:58 Serving a plugin connection...
2022/09/26 18:10:58 packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 plugin: 2022/09/26 18:10:58 [TRACE] starting builder -packer-default-plugin-name-
2022/09/26 18:10:58 packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64 plugin: 2022/09/26 18:10:58 Deprecation warning: Use SCALEWAY_ORGANIZATION environment variable and organization_id argument instead of api_access_key argument and SCALEWAY_API_ACCESS_KEY environment variable.
2022/09/26 18:10:58 Build debug mode: false
scaleway.basic: output will be in this color.
2022/09/26 18:10:58 Force build: false
2022/09/26 18:10:58 On error:
2022/09/26 18:10:58 Waiting on builds to complete...
2022/09/26 18:10:58 Starting build run: scaleway.basic
2022/09/26 18:10:58 Running builder:
2022/09/26 18:10:58 [INFO] (telemetry) Starting builder scaleway.basic
==> scaleway.basic: Prevalidating image name: basic build
2022/09/26 18:11:01 [ERR] Checkpoint error: Get "https://checkpoint-api.hashicorp.com/v1/check/packer?arch=arm64&os=darwin&signature=e22a15bd-14da-807f-90f1-173bb4a873b5&version=1.8.3": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
==> scaleway.basic: error: getting image list: scaleway-sdk-go: error executing request: Get "https://api.scaleway.com/instance/v1/zones/fr-par-1/images?name=basic+build&page=1": dial tcp: lookup api.scaleway.com: i/o timeout
2022/09/26 18:11:03 [INFO] (telemetry) ending scaleway.basic
==> Wait completed after 5 seconds 2 milliseconds
2022/09/26 18:11:03 machine readable: error-count []string{"1"}
==> Some builds didn't complete successfully and had errors:
2022/09/26 18:11:03 machine readable: scaleway.basic,error []string{"error: getting image list: scaleway-sdk-go: error executing request: Get \"https://api.scaleway.com/instance/v1/zones/fr-par-1/images?name=basic+build&page=1\": dial tcp: lookup api.scaleway.com: i/o timeout"}
==> Builds finished but no artifacts were created.
Build 'scaleway.basic' errored after 5 seconds 2 milliseconds: error: getting image list: scaleway-sdk-go: error executing request: Get "https://api.scaleway.com/instance/v1/zones/fr-par-1/images?name=basic+build&page=1": dial tcp: lookup api.scaleway.com: i/o timeout
==> Wait completed after 5 seconds 2 milliseconds
==> Some builds didn't complete successfully and had errors:
--> scaleway.basic: error: getting image list: scaleway-sdk-go: error executing request: Get "https://api.scaleway.com/instance/v1/zones/fr-par-1/images?name=basic+build&page=1": dial tcp: lookup api.scaleway.com: i/o timeout
==> Builds finished but no artifacts were created.
2022/09/26 18:11:03 [INFO] (telemetry) Finalizing.
2022/09/26 18:11:05 [WARN] (telemetry) Error finalizing report. This is safe to ignore. Post "https://checkpoint-api.hashicorp.com/v1/telemetry/packer": context deadline exceeded
2022/09/26 18:11:05 waiting for all plugin processes to complete...
2022/09/26 18:11:05 /Users/frederic/.packer.d/plugins/github.com/scaleway/scaleway/packer-plugin-scaleway_v1.0.6_x5.0_darwin_arm64: plugin process exited
packer build
doesn't work anymore, here is the error :
error creating server: scaleway-sdk-go: http error 410 Gone
From packer version
1.8.4 to 1.11.0
packer {
required_plugins {
scaleway = {
version = ">= 1.0.5"
source = "github.com/scaleway/scaleway"
}
}
}
variable "access_key" {
type = string
sensitive = true
default = ""
}
variable "project_id" {
type = string
sensitive = true
default = ""
}
variable "secret_key" {
type = string
sensitive = true
default = ""
}
source "scaleway" "server_draft" {
access_key = "${var.access_key}"
commercial_type = "PLAY2-PICO"
image = "ubuntu_noble"
image_name = "server-draft"
project_id = "${var.project_id}"
remove_volume = "true"
secret_key = "${var.secret_key}"
server_name = "server-build"
snapshot_name = "server-draft-snapshot"
ssh_username = "root"
zone = "fr-par-2"
}
build {
sources = ["source.scaleway.server_draft"]
}
The Scaleway Packer plugin fails to build an image. This error appears exclusively for block storage SSD images.
packer build -var="scw_commercial_type=DEV1-S" -var "image_size_in_gb=50" -var "image_name=foo" foo.pkr.hcl
From packer version
packer v1.8.1
Plugin version:
v1.0.3
packer {
required_plugins {
scaleway = {
version = "1.0.3"
source = "github.com/hashicorp/scaleway"
}
}
required_version = ">= 1.5.4"
}
# Scaleway image ID or label
variable "scw_image_id" {
type = string
default = "ubuntu_focal"
}
# Scaleway VPS type
variable "scw_commercial_type" {
type = string
}
# Image name is the resuling image name
variable "image_name" {
type = string
}
# Volume size in GB, defaults to 0 for a standard local SSD configuration
variable "image_size_in_gb" {
type = number
default = 0
}
source "scaleway" "foo-image" {
image = var.scw_image_id
commercial_type = var.scw_commercial_type
image_size_in_gb = var.image_size_in_gb
ssh_username = "root"
image_name = var.image_name
}
build {
sources = ["source.scaleway.foo-image"]
}
Tested on MacOS Catalina (10.15.7)
scaleway.foo-image: output will be in this color.
==> scaleway.foo-image: Prevalidating image name: foo
==> scaleway.foo-image: Prevalidating snapshot name: snapshot-packer-1657808327
==> scaleway.foo-image: Creating temporary ssh key for server...
==> scaleway.foo-image: Creating server...
==> scaleway.foo-image: Waiting for server to become active...
==> scaleway.foo-image: Using SSH communicator to connect: 51.15.107.16
==> scaleway.foo-image: Waiting for SSH to become available...
==> scaleway.foo-image: Connected to SSH!
==> scaleway.foo-image: Shutting down server...
==> scaleway.foo-image: Creating snapshot: snapshot-packer-1657808327
==> scaleway.foo-image: Creating image: foo
==> scaleway.foo-image: Error creating image: scaleway-sdk-go: http error 400 Bad Request: snapshot is not available
==> scaleway.foo-image: Provisioning step had errors: Running the cleanup provisioner, if present...
==> scaleway.foo-image: Destroying server...
Build 'scaleway.foo-image' errored after 1 minute 6 seconds: Error creating image: scaleway-sdk-go: http error 400 Bad Request: snapshot is not available
https://github.com/scaleway/packer-plugin-scaleway/blob/main/version/version.go#L7
It should be managed by the CI on release
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
A written overview of the feature.
Any relevant use-cases that you see.
When trying to install the latest version of the Packer plug-in for Scaleway, I get the following error:
$ packer init build.pkr.hcl
Failed getting the "github.com/hashicorp/scaleway" plugin:
1 error occurred:
* could not get sha256 checksum file for github.com/hashicorp/scaleway version 1.0.4. Is the file present on the release and correctly named ? GET https://github.com
/scaleway/packer-plugin-scaleway/releases/download/v1.0.4/packer-plugin-scaleway_v1.0.4_SHA256SUMS: 404 []
It turns out Git tag 1.0.4 exists but not the GitHub release which is supposed to come with it, hence the missing checksum file.
Here is my packer
configuration block:
packer {
required_plugins {
scaleway = {
source = "github.com/hashicorp/scaleway"
version = ">= 1.0.0"
}
}
}
Then just run packer init <filename>
to get the error mentioned in the "Overview of the Issue" section.
Packer v1.8.1.
See "Reproduction Steps" section.
Not relevant.
N/A
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
A written overview of the feature.
Any relevant use-cases that you see.
Add a way to discuss what to do once the image is created. Should I use terraform, or other tools, what are the features that are available?
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
After discussing on slack, it appears image_size_in_gb
's behaviour has changed with the release of unified snapshots..
Would it be possible to update de docs to clarify how this parameter works.
Right now here are the questions I have a hard time answering:
Improve shutdown time and overall packer build times
https://scaleway-community.slack.com/archives/C03B4GW7DFG/p1685450458343039
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
There is some content that could be improved in the documentation:
Required:
@include 'builder/scaleway/Config-required.mdx'
Optional:
@include 'builder/scaleway/Config-not-required.mdx'
The text in https://github.com/scaleway/packer-plugin-scaleway/blob/main/docs/builders/scaleway.mdx should be reviewed by the product documentation team.
Steps to reproduce this issue
From packer version
If the file is longer than a few dozen lines, please include the URL to the
gist of the log or use the Github detailed
format
instead of posting it directly in the issue.
OS, Architecture, and any other information you can provide about the
environment.
Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.
Set the env var PACKER_LOG=1
for maximum log detail.
This issue was originally opened by @OJFord as hashicorp/packer#8191. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
Terraform uses the same environment variables and config files as used by Scaleway's own tooling, unless overridden:
https://www.terraform.io/docs/providers/scaleway/index.html#environment-variables
Packer however uses different environment variables (that sound 'official' enough, but are actually just for packer) and ignores the config file:
https://www.packer.io/docs/builders/scaleway.html#required-
Harmony among tools!
The base image can contain extra volumes but the final generated one will not contain the extra volumes.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
It would be nice to be able to add tags to the created image which would help further search of the app
get all image build with a given version for example
image_tags = list(string)
Hi,
If the env var SCALEWAY_ORGANIZATION is not set, we have the following deprecated message:
Deprecation warning: Use SCALEWAY_ORGANIZATION environment variable and organization_id argument instead of api_access_key argument and SCALEWAY_API_ACCESS_KEY environment variable
If the env var SCALEWAY_ORGANIZATION is set, we have the following deprecated message:
organization_id is deprecated in favor of project_id
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
It would be useful if we add an option to choose to keep or delete the packer instance after a failed build.
The current behavior is to keep the instance.
Having some messages popping up once the image is created could be helpful to hint at other tools such as terraform or the CLI
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
A written overview of the feature.
Any relevant use-cases that you see.
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
I want to be available to filter the image.
Any relevant use-cases that you see.
"source_ami_filter": {
"filters": {
"virtualization-type": "hvm",
"name": "ubuntu/images/*ubuntu-jammy-22.04-amd64-server-*",
"root-device-type": "ebs"
},
"most_recent": true
},
When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.
https://github.com/scaleway/packer-plugin-scaleway/network/updates/845612155
Steps to reproduce this issue
From packer version
If the file is longer than a few dozen lines, please include the URL to the
gist of the log or use the Github detailed
format
instead of posting it directly in the issue.
OS, Architecture, and any other information you can provide about the
environment.
Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.
Set the env var PACKER_LOG=1
for maximum log detail.
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
A written overview of the feature.
Any relevant use-cases that you see.
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
It would be useful to add detailed logs messages such as:
ui.Sayf("Shutting down server (%s) in zone %s", serverID, c.Zone)
That would help customer to see what zone are used and where does this configuration come from.
Debug requests that are generated by customers and pin point misconfiguration of zones/base image.
This issue was originally opened by @mvaude as hashicorp/packer#6776. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
1.3.1
scaleway
cloud-init
and other kind of user-data
could be given in the builder configuration.
As discussed with @sieben, we could migrate to scaleway SDK from @nicolai86 for this kind of features.
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
We should add support for announcements in Slack for every new release:
By using https://goreleaser.com/customization/announce/slack/
Any relevant use-cases that you see.
It would be helpful to have inside the README a complete and functional example of a packer file with the right file name and set of commands to get started.
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
https://code.visualstudio.com/docs/remote/containers
Any relevant use-cases that you see.
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
https://github.com/scaleway/packer-plugin-scaleway/actions/runs/9753370660
In the documentation of the Scaleway Builder there is a param image_size_in_gb
that says we can create an image with block storage but it doesn't work when I try to use it with the image provided by scaleway (here I used: Centos 7.6).
The error given by packer is the following :
==> scaleway: Error creating server: scaleway-sdk-go: http error 400 Bad Request: cannot create a volume of type b_ssd from a base of type l_ssd
Build 'scaleway' errored after 2 seconds 754 milliseconds: Error creating server: scaleway-sdk-go: http error 400 Bad Request: cannot create a volume of type b_ssd from a base of type l_ssd
My packer.json
file looks like that :
"builders": [
{
"image_name": "name-packer-base-block-{{ user `ZONE` }}",
"snapshot_name": "name-packer-base-block-snapshot-{{ user `ZONE` }}",
"image_size_in_gb": "20",
"type": "scaleway",
"image": "centos_7.6",
"zone": "fr-par-1",
"commercial_type": "DEV1-S",
"remove_volume": true,
"ssh_username": "root"
}
],
The feature seems not supported for the moment. Could you please implement custom image creation with block storage in the packer builder?
Creation of custom images with block storage without using the scaleway interface.
Sorry for my English. If you have any questions let me know. I appreciate your help.
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Please vote on this issue by adding a ๐ reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
A written overview of the feature.
Any relevant use-cases that you see.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.