Cleanup machine-specific data

Overview of the Issue

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.

Reproduction Steps

Create any kind of image using packer (even with no steps)
Boot at least two instances based off this image
Observed machine-specific data be shared across instances:
- ssh into the first one, accept its host keys
- ssh into the second one, you will not be prompted to accept its keys as they are the same as the first one

Plugin and Packer version

Latest

Simplified Packer Buildfile

{
  "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"
}

Resolution steps

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:

machine id itself
DUID, which is derived from the machine id
SSH host keys

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:

clear /etc/machine-id (NOT delete it, only clear it)
clear logs generated during packer
cloud-init reset (which holds a cache)
systemd-networkd temporary files and lease file
clear bash_history?
... and more I may not think about

Thanks!

scaleway-sdk-go: http error 400 Bad Request: snapshot is not available

Overview of the Issue

The Scaleway Packer plugin fails to build an image. This error appears exclusively for block storage SSD images.

Reproduction Steps

Set all the required Scaleway environment variables as documented
Run Packer using:

packer build -var="scw_commercial_type=DEV1-S" -var "image_size_in_gb=50" -var "image_name=foo" foo.pkr.hcl

Plugin and Packer version

From packer version

packer v1.8.1

Plugin version:

v1.0.3

Simplified Packer Buildfile

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"]
}

Operating system and Environment details

Tested on MacOS Catalina (10.15.7)

Log Fragments and crash.log files

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

Support tagging the image

Community Note

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.

Description

It would be nice to be able to add tags to the created image which would help further search of the app

Use Case(s)

get all image build with a given version for example

Potential configuration

image_tags = list(string)

Potential References

Always shows a deprecation warning

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

see: https://github.com/scaleway/packer-plugin-scaleway/blame/0b46fa2c9931908d98549d24c2ec73c1c7a206a8/builder/scaleway/config.go#L178

If the env var SCALEWAY_ORGANIZATION is set, we have the following deprecated message:

organization_id is deprecated in favor of project_id

see: https://github.com/scaleway/packer-plugin-scaleway/blame/0b46fa2c9931908d98549d24c2ec73c1c7a206a8/builder/scaleway/config.go#L183

add section about the different configurations option (environment, configuration file, hard coded values, ...)

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.

Community Note

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.

Description

A written overview of the feature.

Use Case(s)

Any relevant use-cases that you see.

Potential configuration

Potential References

Add support for announcements

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.

Community Note

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.

Description

We should add support for announcements in Slack for every new release:

Scaleway community
Internal Scaleway slack

By using https://goreleaser.com/customization/announce/slack/

Use Case(s)

Any relevant use-cases that you see.

Potential configuration

Potential References

Update documentation of `image_size_in_gb`

Community Note

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.

Description

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:

Is it a fixed size the image will take, or just a maximum ?
How does this parameter influences the type of OS disk that is used (local vs block storage) ?

Use Case(s)

Improve shutdown time and overall packer build times

Potential References

https://scaleway-community.slack.com/archives/C03B4GW7DFG/p1685450458343039

Add nightly end to end testing for packer plugin

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.

Community Note

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.

Description

A written overview of the feature.

Use Case(s)

Any relevant use-cases that you see.

Potential configuration

Potential References

Scaleway: add user-data to builder configuration

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.

Packer version: 1.3.1
builder: 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.

@dimtion @edouardb @fflorens @nicolai86 @sieben

Support b_ssd storage with the template images provided by Scaleway

Support block storage in the packer builder with the images provided by scaleway

Description

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?

Use case

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.

review documentation

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

Overview of the Issue

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.

Reproduction Steps

Steps to reproduce this issue

Plugin and Packer version

From packer version

Simplified Packer Buildfile

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.

Operating system and Environment details

OS, Architecture, and any other information you can provide about the
environment.

Log Fragments and crash.log files

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.

dial tcp: lookup api.scaleway.com: i/o timeout

Overview of the Issue

Got strange error about api timeout even if it seems to work when using curl

Reproduction Steps

packer build build_scaleway.pkr.hcl

Plugin and Packer version

1.8.3

Simplified Packer Buildfile

Using the provided exemple in this repo build_scaleway.pkr.hcl

Operating system and Environment details

MacOSX M1-pro Monterey
packer installed through asdf

Log Fragments and crash.log files

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

Add support for HCP packer

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.

Community Note

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.

Description

A written overview of the feature.

Use Case(s)

Any relevant use-cases that you see.

Potential configuration

Potential References

Impossible to install version 1.0.4

Overview of the Issue

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.

Reproduction Steps

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.

Plugin and Packer version

Packer v1.8.1.

Simplified Packer Buildfile

See "Reproduction Steps" section.

Operating system and Environment details

Not relevant.

Log Fragments and crash.log files

N/A

Add documentation about the file that should be deleted or the extra steps performed once an image is created

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.

Community Note

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.

Description

A written overview of the feature.

Use Case(s)

Any relevant use-cases that you see.

Potential configuration

Potential References

feat: block_volume

Community Note

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.

Description

Add attributes to create or import block volumes when starting build instance

Potential configuration

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

Potential References

To fix beforehand: #86

Add logs about what could be done once the image is created.

Having some messages popping up once the image is created could be helpful to hint at other tools such as terraform or the CLI

automate version variable

https://github.com/scaleway/packer-plugin-scaleway/blob/main/version/version.go#L7
It should be managed by the CI on release

generated image does not contains extra volumes

Overview of the Issue

The base image can contain extra volumes but the final generated one will not contain the extra volumes.

Use standard Scaleway env vars / config file

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.

Feature Description

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

"source_ami_filter": {
        "filters": {
          "virtualization-type": "hvm",
          "name": "ubuntu/images/*ubuntu-jammy-22.04-amd64-server-*",
          "root-device-type": "ebs"
        },
        
        "most_recent": true
      },

Potential References

Migrate the example either in the docs/ or in the README

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.

scaleway / packer-plugin-scaleway Goto Github PK

packer-plugin-scaleway's Introduction

Packer Plugin Scaleway

Installation

Using pre-built releases

Using the packer init command

Using the packer plugins install command

Manual installation

From Sources

Configuration

Contributing

packer-plugin-scaleway's People

Contributors

Stargazers

Watchers

Forkers

packer-plugin-scaleway's Issues

Overview of the Issue

Reproduction Steps

Plugin and Packer version

Simplified Packer Buildfile

Resolution steps

Overview of the Issue

Reproduction Steps

Plugin and Packer version

Simplified Packer Buildfile

Operating system and Environment details

Log Fragments and crash.log files

Community Note

Description

Use Case(s)

Potential configuration

Potential References

Community Note

Description

Use Case(s)

Potential configuration

Potential References

Community Note

Description

Use Case(s)

Potential configuration

Potential References

Community Note

Description

Use Case(s)

Potential References

Community Note

Description

Use Case(s)

Potential configuration

Potential References

Support block storage in the packer builder with the images provided by scaleway

Description

Use case

Overview of the Issue

Reproduction Steps

Plugin and Packer version

Simplified Packer Buildfile

Operating system and Environment details

Log Fragments and crash.log files

Overview of the Issue

Reproduction Steps

Plugin and Packer version

Simplified Packer Buildfile

Operating system and Environment details

Log Fragments and crash.log files

Community Note

Description

Use Case(s)

Potential configuration

Potential References

Overview of the Issue

Reproduction Steps

Plugin and Packer version

Simplified Packer Buildfile

Operating system and Environment details

Log Fragments and crash.log files

Community Note

Description

Using the `packer init` command

Using the `packer plugins install` command