packer vs docker for container provisioning

[Sudeep Sukumar]

Hello,

I am a newbie here. I was looking into packer for container provisioning (not VM) and at the moment packer looks more like an unnecessary abstraction to me. I could very well do all I need with docker (in Dockerfile) itself. So I was just wondering what packer brings extra to the table for container provisioning that I could not do with a simple docker and Dockerfile. Could anyone enlighten me with some extra benefits one experienced with packer for container provisioning compared to docker?

Thanks!

Sudeep

[Rickard von Essen]

The big uses case for building Docker images with Packer is when you
want to ship your application as both a VM image and a Docker image or
when you have a lot of legacy provisioning (Puppet, Chef etc) which is
cumbersum to run in a Dockerfile without creating lots of layers.

And you can also use it for building complex Docker images without a
lot of layers.

// Rickard

> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/82b7fa6b-00f8-4c78-ad15-fbb4e5b1e057%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Sudeep Sukumar]

Thanks Rickard!

So for my minimal container provisioning for microservices, this seems like an overkill.

Many thanks

Sudeep

> email to packer-tool+unsubscribe@googlegroups.com.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/82b7fa6b-00f8-4c78-ad15-fbb4e5b1e057%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---

You received this message because you are subscribed to a topic in the Google Groups "Packer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/packer-tool/dkAV0AL50Jc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt8TFr6u6ZpgAqBZF%3DOE%3DjAVgtptgNifKnJ4rWazyH73BQ%40mail.gmail.com.

[Alvaro Miranda Aguilera]

depends.

If also does more than just run docker-build

it will pull an image, run scripts inside the docker, then you could tag the the image, optionally push to the regestry.

If you want to do the same you end with multiple scripts.

Alvaro.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAEE2JqYMt%3DTr__Fh8pRTyFcZhooiWX-ZfRi3vYiB50HMHwQEeA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro