iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Initial documentation for VirtualBox SSH key pair vars.

This commit is contained in:
Stephen Fox 2019-02-06 16:03:40 -05:00
parent b7719650ae
commit 0378f3ad35
3 changed files with 66 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/builders/virtualbox-iso.html.md.erb
View File

@ -375,6 +375,8 @@ contention. If you notice missing keys, you can tune this delay by specifying
<%= partial "partials/builders/boot-command" %>
<%= partial "partials/builders/virtualbox-ssh-key-pair" %>
Example boot command. This is actually a working boot command used to start an
Ubuntu 12.04 installer:

2
website/source/docs/builders/virtualbox-ovf.html.md.erb
View File

@ -317,6 +317,8 @@ contention. If you notice missing keys, you can tune this delay by specifying
<%= partial "partials/builders/boot-command" %>
<%= partial "partials/builders/virtualbox-ssh-key-pair" %>
Example boot command. This is actually a working boot command used to start an
Ubuntu 12.04 installer:

62
website/source/partials/builders/_virtualbox-ssh-key-pair.html.md Normal file
View File

@ -0,0 +1,62 @@
### SSH key pair automation
The VirtualBox builders can inject the current SSH key pair's public key into
the template using the following variables:
- `SSHPublicKey` (*VirtualBox builders only*) - The SSH public key as a line
in OpenSSH authorized_keys format.
- `EncodedSSHPublicKey` (*VirtualBox builders only*) - The same as
`SSHPublicKey`, except it is URL encoded for usage in places
like the kernel command line.
When a private key is provided using `ssh_private_key_file`, the key's
corresponding public key can be accessed using the above variables.
If `ssh_password` and `ssh_private_key_file` are not specified, Packer will
automatically generate en ephemeral key pair. The key pair's public key can
be accessed using the template variables.
For example, the public key can be provided in the boot command:
```json
{
"type": "virtualbox-iso",
"boot_command": [
"<up><wait><tab> text ks=http://{{ .HTTPIP }}:{{ .HTTPPort }}/ks.cfg PACKER_USER={{ user `username` }} PACKER_AUTHORIZED_KEY={{ .EncodedSSHPublicKey }}<enter>"
]
}
```
The kickstart can then leverage those fields from the kernel command line:
```
%post
# Newly created users need the file/folder framework for SSH key authentication.
umask 0077
mkdir /etc/skel/.ssh
touch /etc/skel/.ssh/authorized_keys
# Loop over the command line. Set interesting variables.
for x in $(cat /proc/cmdline)
do
case $x in
PACKER_USER=*)
PACKER_USER="${x#*=}"
;;
PACKER_AUTHORIZED_KEY=*)
encoded="${x#*=}"
# URL decode $encoded into $PACKER_AUTHORIZED_KEY
printf -v PACKER_AUTHORIZED_KEY '%b' "${encoded//%/\\x}"
;;
esac
done
# Create/configure packer user, if any.
if [ -n "$PACKER_USER" ]
then
useradd $PACKER_USER
echo "%$PACKER_USER ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers.d/$PACKER_USER
[ -n "$PACKER_AUTHORIZED_KEY" ] && echo $PACKER_AUTHORIZED_KEY >> $(eval echo ~"$PACKER_USER")/.ssh/authorized_keys
fi
%end
```