News for hackers. Stuff that matters.
Re:Docker Compose reads your “.env” without opt-out by LethargicStud on Thursday October 17, 2019 @02:10PM (#21284817)
This is the exact class of problem that docker itself attempts to avoid. This is why I run docker-compose inside a docker container, so I can control exactly what it has access to and isolate it. There's a guide to do so here[1]. It has the added benefit of not making users install docker-compose itself - the only project requirement remains docker.

1: https://cloud.google.com/community/tutorials/docker-compose-...

Re:Docker Compose reads your “.env” without opt-out by djsumdog on Thursday October 17, 2019 @02:14PM (#21284864)
> docker-compose inside a docker container

Do you use Docker-in-Docker or do you mount the docker socket inside your docker-compose container?

Oh dear god .. it's Docker all the way down.

Re:Docker Compose reads your “.env” without opt-out by LethargicStud on Thursday October 17, 2019 @02:19PM (#21284921)
Mount the docker socket. There's some quirks with storage volume paths. Also, security implications. Was not super hard to get working though.

I'd love to go straight to containerd or even basic linux containers but I'm not willing to run kubernetes on my personal machine and haven't found any ergonomic enough ways to run containers.

Re:Docker Compose reads your “.env” without opt-out by seabrookmx on Thursday October 17, 2019 @07:36PM (#21287331)
Check out https://podman.io?

Like docker (uses CRI images) but daemonless.

Re:Docker Compose reads your “.env” without opt-out by yjftsjthsd-h on Thursday October 17, 2019 @10:53PM (#21288273)
I thought it didn't even support compose like functionality? Or did they add that now?
Re:Docker Compose reads your “.env” without opt-out by rumanator on Friday October 18, 2019 @03:18AM (#21289304)
Docker-compose is an add-on script that only automates how containers are launched/shut down.
Re:Docker Compose reads your “.env” without opt-out by toma1k on Friday October 18, 2019 @03:33AM (#21289369)
Re:Docker Compose reads your “.env” without opt-out by hosh on Thursday October 17, 2019 @03:31PM (#21285572)
I'm more than willing to run K8S on my personal machine in the form of microk8s, k3s, minikube, and similar cut-down versions of k8s.
Re:Docker Compose reads your “.env” without opt-out by arcticfox on Thursday October 17, 2019 @05:49PM (#21286664)
The others are probably fine, but for anyone thinking about this, minikube uses 50% CPU even on powerful machines for no reason [0]. I switched to kind and it works perfectly, super lightweight.

[0] https://github.com/kubernetes/minikube/issues/3207

Re:Docker Compose reads your “.env” without opt-out by hosh on Thursday October 17, 2019 @08:08PM (#21287506)
I have used minikube before. Back when it was using localkube, it was ok. It isn't as much now. (Now, it uses kubeadm to bring up the full suite).

microk8s might not give as much gains.

k3s from Rancher actually cuts out a lot of code, and from I hear, can run fine on Rapsberry Pis.

I have not heard of "kind", but neat.

Re:Docker Compose reads your “.env” without opt-out by verdverm on Thursday October 17, 2019 @08:15PM (#21287547)
Using the KVM driver reduces minkube cpu waste a lot, only supported on Linux...
Re:Docker Compose reads your “.env” without opt-out by idnefju on Thursday October 17, 2019 @08:43PM (#21287684)
do you have any article links about your kind setup?
Re:Docker Compose reads your “.env” without opt-out by hosh on Friday October 18, 2019 @10:25AM (#21291619)
I don't know about the other guy's setup, but here's the github repo: https://github.com/kubernetes-sigs/kind

KIND - Kubernetes In Docker