Skip to content

Conversation

@wking
Copy link
Contributor

@wking wking commented Aug 16, 2018

Builds on #1; review that first.

So you can run the container as if it were a terraform executable installed on your host system. I'm not sure if/how the previous fmt example worked without this.

wking added 3 commits August 16, 2018 10:49
Relative paths like 'terraform' are expanded form the current working
directory anyway, so we don't need this extra command substitution.
Using the JSON array syntax to get:

  # podman inspect terraform-scratch:v0.11.7 | jq '.[0].ContainerConfig.Entrypoint'
  [
    "/terraform"
  ]

With --entrypoint=/terraform, you'd get:

  [
    "/bin/sh",
    "-c",
    "/terraform"
  ]

and this container doesn't have /bin/sh.
Avoiding:

  # podman run terraform-scratch:v0.11.7 --help
  Couldn't setup logging tempfile: open /tmp/terraform-log820361243: no such file or directory
@wking wking force-pushed the terraform-from-scratch-entrypoint branch from f892de7 to f3c4c47 Compare August 16, 2018 18:11
@sallyom sallyom merged commit e12e99d into sallyom:master Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants