3 ms·

Neither k3d (k3s) nor kind support building of images since they use containerd directly, which [building] seems to be a requirement for development environment

• gravypod 6y ago
  Yea, exactly, this. I see all sorts of people making build systems and tools and they say you just do "my_command build my_target && docker-compose up -d" and I can't help but wonder: are these people ONLY developing 1 service? For me, that would be multiplied by 20x and we're not even at the number of services we're expecting. We do a lot of integration with third parties which is essentially pull down some data and write it into a microservice responsible for keeping that data. Each of these integrations is owned by a separate engineer because it takes up a lot of time to deal with integration calls, planning, etc and we need to be language flexible (some people only give you a .dll or .jar, no choices). I'm assuming people building these tools don't use a local development workflow because: their systems are too big to run on a single machine (Googlers) or don't work on large projects (open source side projects). The clostest thing to what you and I are looking for, though, is skaffold and tilt.dev.
• moondev 6y ago
  Have you tried building images from inside a pod via buildah?
• oldman_peter 6y ago
  I use a `buildah` to build images in a k3s container. You'll have to enable user_namespace at boottime on your k3s host though.