#terraform-tool

hey guys... anyone have any tips on dealing with RDS instances?

if I just follow the example in the docs I run into "DB instance already exists error" when I reapply the terraforms

Good morning guys, I am looking to pull the latest 0.6.9 dev release, which branch is this on Github?

hello

trying to debug why I'm getting a prompt when I am reasonably sure I'm setting the variable value when referencing the module. How do you suggest debugging why I'm getting a prompt?

good morning and happy new year everyone :)

happy new year :)

Hello.

Is there a better way than just echoing an AWS instance IP to a file in another instance to force ordering?

sounds like you need the "depends_on" attribute;

so in instance2 you can add an attribute that says "depends_on ["aws_instance.instance_1"]

jedineeper: Exactly! I knew i must be missing something :-)

jedineeper: Thank you.

np :)

I asked this before... but no answer.... I am looking to pull the latest 0.6.9 dev release, which branch is this on Github?

you want the latest code? then just pull from master

the bleeding edge code (0.6.9-dev) is merged into there

Oh ok

Cheers

can terraform touch dockerfiles ? Eg. dockerfiles contain variables and you fill this variables via terraform and build it like that

livcd: wouldnt you want to use packer for that?

no why ?

I can't see how your building Docker containers as part of terraform? Isn't the construction of the artifact a pre-step to that?

jedineeper: actually i did not know that packer can handle docker as well :D

but i'll take a look

so i can build and publish docker containers via packer to hub.docker as well ?

yep (I do myself)

I'll definitely take a look at that

oh it's a bit inconvenient for me

While Docker has many features, Packer views Docker simply as an LXC container runner.

but docker is not "LXC" anymore

Hmm, I was aware that there was an outstanding issue regarding building up the docker container layers via packer but not something as drastic as that

(sorry, fire evac drill, urgh)

uhh

well so i wonder if it builds an actual docker containers or...

boxrick1: I just build it off the master branch

ah, someone got you already

livcd: it builds actual docker containers - at least I was publishing them to docker hub and reusing them elsewhere?

jedineeper: ok ok thanks

jedineeper: so what is actually the issue with packer+docker ? :P

(in my limited docker understanding) a regular dockerfile will build your image in layers to reduce buildtime in future iterations? Packer will always rebuild the whole layer as one layer every time..

However, I could be talking crap because i can't fdin the issue in the packer github issues list anymore

I haven't built them with Docker, but a normal 'docker build' doe the layer think that jedineeper speaks of.

s/with Docker/Packer/

if Packer spins up a VM before the build though and then tears it down, that layer cache will of course go away and it'll jsut rebuild the whole thing every time.

also why you craft your Dockerfile carefully to be able to keep those layers that don't change.

i wish Packer would be able to connect to docker daemon remotely

"builder/docker: Now works remote hosts, such as boot2docker [GH-2846]" is in the release notes for the next version of packer

(I've no idea if this is what you mean, I'm talking out of my depth re: docker and should probably quit while I'm ahead)

hah

yeah, that's what I'm talking about.

Packer just sets up the build environment and runs scripts you tell it too though. Isn't it possible to script connecting the docker daemon?

well i do not want to install a packer to the host i want to run the packer from my laptop and point it to any machine that has docker daemon

ahh