I realize this is not a packer issue, per se, but I'm hoping someone has
been through this process with their image.
As per the "unmanaged disks are being deprecated" warning (from packer?), I
switched to using managed disks for Azure. *Has anyone, in the history of
the universe, been able to publ
I'm new to docker, so maybe this is just my ignorance, but does adding
docker labels actually work with packer?
9 "builders": [{
> 10 "type": "docker",
> 11 "image": "ubuntu:18.04",
> 12 "export_path": "output-docker/akm-{{user `akm_version`}}-u{{user
> `u_version`}}-{{user `bui
:
> "/var/lib/docker/overlay2/7a747e66900365c1a537cc8d11f9b226304211c22a13fea5be57a698cd5aea1a/diff",
> "WorkDir":
> "/var/lib/docker/overlay2/7a747e66900365c1a537cc8d11f9b226304211c22a13fea5be57a698cd5aea1a/work"
> },
>
; sha256:f36adac65043d944f1e4f3d8764766f3238475d317785279f333838ce0e7889a
>
> $ docker inspect
> sha256:f36adac65043d944f1e4f3d8764766f3238475d317785279f333838ce0e7889a
> --format "{{ .Config.Labels }}"
> map[foo:bar]
>
>
> On Tue, Mar 19, 2019 at 4:57 PM 'Nich
lost.
>
> On Tue, Mar 19, 2019, 19:15 'Nicholas Bayle' via Packer <
> packer-tool@googlegroups.com> wrote:
>
>> No dice. Is it safe to assume that "changes": [] only works with *commit*,
>> not *export_path*?
>>
>> On Tue, Mar
Hello, when using docker save in general, you can specify tags. See:
https://docs.docker.com/engine/reference/commandline/#cherry-pick-particular-tags
However, with the docker-save post-processor, there doesn't appear to be a
way to tag the exported image.
I looked at the docker-tag post-processo
r docker-tag.
>
> On Mon, Apr 29, 2019, 23:46 'Nicholas Bayle' via Packer <
> packer-tool@googlegroups.com> wrote:
>
>> Hello, when using docker save in general, you can specify tags. See:
>>
>> https://docs.docker.com/engine/reference/commandline/#cherr
, May 1, 2019 at 1:10 AM Rickard von Essen <
rickard.von.es...@gmail.com> wrote:
> Does it work as you expect if you do it manually with the docker cli?
>
> On Tue, Apr 30, 2019, 17:31 'Nicholas Bayle' via Packer <
> packer-tool@googlegroups.com> wrote:
>
>
e0fa25854 days
> ago 102MB
>
>
> Thank you,
> Nick
>
> On Wed, May 1, 2019 at 1:10 AM Rickard von Essen <
> rickard.von.es...@gmail.com> wrote:
>
>> Does it work as you expect if you do it manually with the docker cli?
>>
>> On Tu
ine": ["rm /tmp/manifest"]
}
],
"post-processors": [
{
"type": "shell-local",
"inline": ["mv manifest manifests/manifest-akm-{{user
`akm_version`}}-u{{user `u_version`}}-{{user `build_stamp`}}-docker.txt"]
},
; "type": "docker-save",
> "path": "output-docker/akm-{{user `akm_version`}}-u{{user
> `u_version`}}-{{user `build_stamp`}}.tar"
> }
> ]
> ]
>
> On Mon, May 6, 2019 at 5:41 PM 'Nicholas Bayle&#
Is there a trick to creating a file in the filesystem root (/) using a
provisioner? I cannot get past the permission denied, even with sudo, yet
the chef provisioner that follows runs fine and can modify everything.
28 {
29 "type": "shell",
30 "inline": ["echo 'vagrant' | sudo -
Always a pleasure.
On Thu, May 30, 2019 at 10:40 AM Rickard von Essen <
rickard.von.es...@gmail.com> wrote:
> See https://stackoverflow.com/q/82256/226174
>
> On Thu, May 30, 2019, 18:31 'Nicholas Bayle' via Packer <
> packer-tool@googlegroups.com> wrote:
>
&
So I'm trying to merge multiple packer json files together using the
following json files:
- variables used by all platforms
- platform-specific requirements (usually a builder & sometimes a
provisioner and/or post-processor)
- the provisioners used for all platforms
- the post-processors used by a
So everybody just does copy/paste and manages multiple files by hand? A
nightmare indeed.
On Thu, Sep 5, 2019 at 4:13 PM Nicholas Bayle <
nicholas.ba...@townsendsecurity.com> wrote:
> So I'm trying to merge multiple packer json files together using the
> following json files:
> - variables used b
For posterity, here is how you do it:
jq -s '[.[] | to_entries] | flatten | reduce .[] as $dot ({}; .[$dot.key]
+= $dot.value)' file1.json file2.json fileN.json | packer build -
On Tue, Sep 10, 2019 at 10:37 AM Nicholas Bayle <
nicholas.ba...@townsendsecurity.com> wrote:
> So everybody just does
Well, let me see if I'm even using the right tool, before we head down the
rabbit hole.
My goal is to generate mostly identical images in various formats (ovf,
ami, vhd, etc), customized using chef-solo. I'd like to start with a nicely
pared down ubuntu image. My original plan was to simply do thi
one source per
> platform and do the same manipulations on each of the.
>
> Why don't you just enable head? (headless: false)
> And can you describe how you try to connect with VRDP?
>
> On 12 July 2017 at 19:51, 'Nicholas Bayle' via Packer
> wrote:
>
do the same manipulations on each of the.
>>
>> Why don't you just enable head? (headless: false)
>> And can you describe how you try to connect with VRDP?
>>
>> On 12 July 2017 at 19:51, 'Nicholas Bayle' via Packer
>> wrote:
>> > Well
When completing an Azure build with packer, it displays the temp vhd it's
going to delete:
azure-arm: -> OS Disk : '
https://blahblah.blob.core.windows.net/images/pkros07vy57rjy5.vhd'
What would be handy is displaying the final artifact vhd you have to use:
https://blahblah.blob.core.windows.ne
azure/arm/builder.go
>
> Thanks
> Alvaro.
>
> On Wed, Jan 10, 2018 at 9:47 PM, 'Nicholas Bayle' via Packer <
> packer-tool@googlegroups.com> wrote:
>
>> When completing an Azure build with packer, it displays the temp vhd it's
>> going to delete:
I had this issue.
The problem occurs when the host VM has permission to "monitor all traffic"
on the parent host. The DHCP request ends up going outside the VMware host
(despite whatever your nat/hostonly settings are) to the parent VMware
installation or external DHCP server. You can verify this
22 matches
Mail list logo
