Comments (3)
Hi @thomasjcf29, thanks for the feature request! In order to better understand the problem, can you tell us a little bit more about the situation you are facing?
So a basic Packer workflow is:
- Packer initializes a machine with a private or public image.
- Packer creates another private image with the machine it initialized above.
- The Packer created private image is ready and being deployed to Linodes for production/development use.
Adding the Config support in Packer will only let you use GRUB2 kernel in the step 1.
If you are looking for using GRUB2 kernel in step 3 without doing explicit Config and Disks creation API calls, we will have to make a further feature request to other teams because a Linode kernel will still be used when the Linode is created with a private image (built by Packer), and Packer plugin alone can't support it as it's outside of the Packer run period.
May I know where you are looking for using the GRUB2 kernel? Maybe both?
And due to known limitations, if Packer allows you to create a explicit Config, then you will also have to define the explicit disks for the Linode used for building the image, which may be complicated.
It will be something like:
source "linode" "example" {
instance_type = "g6-nanode-1"
region = "us-mia"
ssh_username = "root"
config {
// other fields...
sda {
disk_label = "boot disk"
}
}
disk {
label = "boot disk"
image = "your_image"
size = 12345 // optional
// other fields...
}
}
May I know if that looks okay to you?
from packer-plugin-linode.
Hi @zliang-akamai thanks very much for getting back to me!
Yes, I'm looking to do it on the stage 1, so the image which has been launched by packer for the destination image to be created.
The use case for this is that we would like to confirm our golden images can be booted with how we expect them to be booted in production.
The config object makes sense to me, does it make sense to have defaults / use the default config created by Linode and then override where required rather than specifying defaults? Although if that's not possible I don't mind specifying defaults as it will be a common local block that I can share with all my images.
Ultimately, I just want to change the kernel before the packer image is launched (but after it's created), so having defautls would make sense. However, specifying other config objects is fine by me as well :))
Many Thanks,
Tom Franklin.
from packer-plugin-linode.
@thomasjcf21 Thanks for the details and the suggestion! We will be considering all options and tracking this issue internally.
from packer-plugin-linode.
Related Issues (9)
- linodego version HOT 1
- Dep linodego v1.0.0 does not exist. HOT 2
- Setting ssh_private_key_file fails with linode error HOT 1
- Support for private ips HOT 3
- [Bug]: OAuth error with plugin versions > 1.0.5 HOT 2
- [Bug]: Tags are not applied when building using Packer
- [Bug]: Equal (=) sign is not being accepted as a tag value
- Packer 1.12.0-alpha1 testing HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from packer-plugin-linode.