detecting a Dockerfile and building an image?

[rcarmo]

Hi great work on this. Is it possible to push an arbitrary dockerized app to Piku and skip any auto detection on the source code by simply detecting a Dockerfile and building an image out of that?

Originally posted by @IRobL in #11 (comment)

[rcarmo]

• that’s (a subset of) what dokku does, and piku was developed specifically for use in scenarios where I can’t use Docker, or where it would be forbiddingly expensive CPU-wise
• building images also means managing the entire lifecycle (cleaning out old images, etc.)
• I’d have to have radically different logic for restarting services (right now incron checks if there are any .ini file changes and nudges uwsgi, which is nice and neat and only happens after I write out a service config, magically)
• I’d have to deal with network ports and re-jigger the nginx mapping, ports and whatnot, which is something I have kept simple on purpose

I use docker-compose a lot, though, so I might eventually get round to it, and I would be fine with taking a pull request for that (although I think we’d have to keep the Procfile as well unless a compose YAML was present, because app settings have to live someplace).

[IRobL]

Thanks for the great response! I'm looking for a container solution for learning a new lang. So I take it the current state of docker on RPI is that docker-compose is working well? While I sure love Heroku style deploys, if docker-compose and docker-swarm are available, I may go that way with it until a push-to-deploy system for docker images comes along.

[rcarmo]

I've been using docker-compose for many months now without issues (other than having to build ARM containers for many things). I've since started moving to k3s, which is a bit overkill but also working.

[rcarmo]

I'm also going to file this as a "won't fix" by design ;)