alternative to container resource

[drahnr]

Feature Request

What challenge are you facing?

Currently the docker resource consumes a docker file and all the heavy lifting is done in the resource.
The docker approach also causes huge spikes in worker load for some reason and the resource itself is quite complex.
Another reason is that I think that Docker is not a good solution for containerization nor are Dockerfiles an adequate description of a container.

A Modest Proposal

Use another tooling such buildah ( https://github.com/projectatomic/buildah ) to run a arbitrary command in the context and push the resulting image as container to a registry.
This would match the whole concourse pipeline idea of input / output way better.

This is something I've been thinking about for a while and would like to spark a discussion / feedback on what people's painpoints are (if any!).

[marco-m]

I cannot google anything useful for ahbuild. Could you please give some pointers ?

[drahnr]

@marco-m added a link, ah was a postifx, not prefix. Corrected.

[vito]

Very similar discussion has been had in concourse/docker-image-resource#190 - leading to a Kaniko task example

[stale]

Beep boop! This issue has been idle for long enough that it's time to check in and see if it's still important.

If it is, what is blocking it? Would anyone be interested in submitting a PR or continuing the discussion to help move things forward?

If no activity is observed within the next week, this issue will be exterminated closed, in accordance with our stale issue process.