devspace VS kaniko

Check also devspace.sh and okteto.com

There is actually a built-in converter from docker-compose.yaml to devspace.yaml, it is part of the "devspace init" command. There are a few known issues related to it, in case you would like to contribute :)

Wrapping https://devspace.sh in my company's internal CLI to improve development experience

For Kubernetes clusters, https://devspace.sh/ allows you to iterate on your app in a running pod from your IDE. No ci/cd pipeline, no re-applying manifests; it just uploads source code from your local machine and restarts your app for you in an existing pod. Pretty slick!!! But it requires K8s, so some devs may balk at it. (Tilt and Skaffold do the same thing)

We’re excited to announce that DevSpace version 6 has been released. Thanks to everyone who used the alpha and beta versions and gave us feedback.

DevSpace is free, lets you develop natively in the cloud on any K8s cluster. Compatible with any multitenancy solution, policy governance, etc. Works with your IDE of choice. Declarative configuration. Supports custom pipelines and deploy logic. Can link multiple environments together. https://devspace.sh/

My favourite tool in this category is Devspace. As you've requested it is capable of building and deploying multiple images.

If all you need to do is build container, you can use https://github.com/GoogleContainerTools/kaniko

Kaniko for building the container images

kaniko

You should maybe look into Kaniko or use some other build tool

If you are using the docker socket just for building container images, you might want to look into kaniko. It doesn't use docker to build images. If you use the socket also for starting containers (we are actually doing that in our CI pipelines), you could think about limiting the pods Kubernetes schedules on a node (you can change the default of 110 using the kubelet config file).

Check out Kaniko for building containers https://github.com/GoogleContainerTools/kaniko . Only issue is it doesnt support windows containers.

It took less than 5 minutes to install. It quickly analysed the repo and identified easy ways to make the project more secure. Priya Wadhwa, Kaniko

I'd suggest to take a look at the Kaniko project, combined with custom container images in Lambda functions.

kaniko is a tool that allows you to build container images inside Kubernetes without the need for the Docker daemon. Effectively, it allows you to build Docker images without docker build.

Kubernetes prefers to pull containers from registries. You may be able to work around it by specifying a local image in your Kube manifest. Both https://github.com/GoogleContainerTools/kaniko and/ or https://www.devspace.sh/ may help.