31–40 of 45 posts
To the container wizards: Is it possible to orchestrate lxc containers using kubernetes? I've been looking at lxc containers for a while and really would not like to run Docker as root.
Earlier quoted context omitted.
Would you be willing to elaborate on the reason why you avoid kubernetes?
I'm not the OP, but... Here's the scene: Most of the web projects I work on will never have a billion users. They might have 5, or 10. One or two have thousands. Several of them have 1 (me). Docker-compose works for me. I set up a container for my backend, a container for whatever's serving the static resources for the frontend, and a container for whatever databases are needed (Postgres, Redis, whatever). The databa…
Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
Earlier quoted context omitted.
I don't like their idea of what a docker-compose replacement should be. And reading issues and limitations about podman pod commands is very discouraging. I would love to hear what others are using and their experiences though. I avoid anything Kubernetes because of a personal bias.
Would you be willing to elaborate on the reason why you avoid kubernetes?
The cost of running a managed kubernetes is too expensive to justify for the benefits in these cases. And if you choose to self-manage to cut the money cost, it ends up being significantly more expensive from a time and sanity perspective.
Earlier quoted context omitted.
I'm not the OP, but... Here's the scene: Most of the web projects I work on will never have a billion users. They might have 5, or 10. One or two have thousands. Several of them have 1 (me). Docker-compose works for me. I set up a container for my backend, a container for whatever's serving the static resources for the frontend, and a container for whatever databases are needed (Postgres, Redis, whatever). The databa…
I like the sound of how you have that set up, do you know any good open source repositories that are designed the way you describe that I could look at for learning purposes? (I mean, projects that set up containers for backend, database, and front-end servers and push them to digitalocean etc.. I can imagine how each piece works, but I'd love to see how a coherent and manageable project in that style is organized as…
Earlier quoted context omitted.
Comparing the shortcomings of rootless podman ( https://github.com/containers/libpod/blob/master/rootless.md ) and rootless docker, they seem almost the same. So this argument may not count, the daemon argument however applies.
I wonder if we will ever get rid of the ludicrous limitation of the privileged ports. It's a mechanism that only provided some sense of security in the 80s. The W3C[1] says "if you connect to a service on one of these ports you can be fairly sure that you have the real thing, and not a fake which some hacker has put up for you." Well, in 2019 computers aren't mainframes run by institutions and hackers can be root of…
sysctl net.ipv4.ip_unprivileged_port_start=443
( https://stackoverflow.com/questions/413807/is-there-a-way-fo... )
Earlier quoted context omitted.
The thing is, I don't even really like Docker as an init daemon. I have my gripes about Systemd but I see no downsides to not having a long-running daemon for a container engine. Really, whether you need root or not isn't even the most important issue; you can do sudo or suid or whatever with any container engine; Docker just has it be an implicit, unintuitive behavior. I used to use systemd+rkt for simple container…
I read an article (can't find it now) that said from a previous project the Docker authors concluded they wanted a daemon so they didn't have to do things like file locks, etc. around image management. Don't know if that accounts for the whole reason or not.
https://jpetazzo.github.io/2017/02/24/from-dotcloud-to-docke...?
Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
What are my options to replace Docker Compose? I dont want to introduce a chaotic mess by using kubernetes. Or to dedicate brain power to learn what they changed every week. Their readme really confuses me with podman play, kompose, k8s.
Earlier quoted context omitted.
What are my options to replace Docker Compose? I dont want to introduce a chaotic mess by using kubernetes. Or to dedicate brain power to learn what they changed every week. Their readme really confuses me with podman play, kompose, k8s.
There is an implementation of docker compose for podman in development: https://github.com/muayyad-alsadi/podman-compose
>https://github.com/muayyad-alsadi/podman-compose/issues/13
Hard to trust a repo like that for production.
Unless Red Hat provides an alternative I won't be able to use podman. IIRC they said it was too hard to keep up with K8S changes so even an abstraction for that would be too costly.
Earlier quoted context omitted.
I like the sound of how you have that set up, do you know any good open source repositories that are designed the way you describe that I could look at for learning purposes? (I mean, projects that set up containers for backend, database, and front-end servers and push them to digitalocean etc.. I can imagine how each piece works, but I'd love to see how a coherent and manageable project in that style is organized as…
Hmmmm... I can't say I've ever looked a whole lot. Based on the replies in this thread though, I should probably just take the scripts I've got, make sure there's nothing sensitive in there, and throw them up on Github. Maybe I'll strip my SSH pubkey out of the too, so that we don't end up with a bunch of servers that I can log into :D