I am primarily a backend dev but I always had a secret affair with 'systems' level things. For the past 3 months I've been dragged into managing the DevOps of a small startup. Being a fan of good tools (and not caring about the status quo), I immediately resorted to using Docker containers and tools like Traefik for easing reverse proxy, load balancing, SSLs and what not. Soon I realized that there was whole new world out there that I never knew learned about in my undergrad studies (class of '19).<p>But very soon I also realized that Docker (the only containarization tool I've used) has a lot of weaknesses. For some fun (and profit?) I would want to work on fixing few things. What are your main pains using containers?<p>Here's my list (but could be completely uninformed and that's why I'm here):
1. Lack of `hot reloading` kind of thing. I don't mean application wise but container wise. It's not so much fun attaching or changing a port in a container on the fly.
2. Caches. It's not transparent at all when and why and where caches were used. I mean once you're a pro it's quite easy(?), but for beginners it's really painful.
Have you looked at awesome-docker, docker-compose, gVizor, Kubernetes / KIND / k3s, telepresence.io<p>Why would you change a port on the fly?<p>fyi, there is not really money at the container level. See recent events with Docker the company.<p>cncf.io is another thing to check out