that is fine, the only requirement AFAIK is the user being in the docker group in case you're having permission issues running it as user
post
I don't understand the question tbh. Make a docker-compose.yml in some folder, and then run your docker compose commands in that folder. Does that result in error and if so what errors?
Compose is just a single binary. There is no wrong way to install it really as long as it can find all the needed shared libraries and such.
If in doubt, look at the manual install instructions. Run through that, and see if it behaves any differently.
Some logs from the startup of a this container would help. Just run docker compose up (without the -d) and you'll get all the output up front.
Or you know, move on to newer better tools that even docker uses internally instead of this limpdick unsupported tool.
Use kind, and kubernetes resources. You can literally use ‘kompose’ to convert your compose config, and then apply it to a local kind cluster.
all 7 comments