5 ms·

More love needs to go into docker-compose for podman. https://github.com/containers/podman-compose https://github.com/containers/podman-compose

by geenat 5y ago

jordemort 5y ago
I've been using regular old docker-compose with podman since podman 3.2.0. You need to enable the podman socket, which kind of takes away some of the daemonless fun, but once you do that (and point your DOCKER_HOST at the appropriate location), you can "docker-compose up" and it will just work.
ron0c 5y ago
I used to think so until I started just using bash scripts in replacement of docker-compose files.
- ageofwant 5y ago
  What is your bash depends_on: equivalent ? I like the idea of keeping it simple bash, but seems like it is a step back.
  - arve0 5y ago
    I’ve used wait-for-it with success. https://github.com/vishnubob/wait-for-it https://github.com/vishnubob/wait-for-it
  - ron0c 5y ago
    I had to look up what depends_on accomplishes, so maybe I'm missing something here, but wouldn't an If/then/else sort that out as well as give you more options?
- lucb1e 5y ago
  Anecdotally, and perhaps keep in mind I'm quite skilled with bash, in school we had a few people managing their desktops with scripts. Set things like desktop preferences, ssh config, sometimes add a different desktop environment (we each had our own user and it worked with LDAP, so we roamed around and that's why this was useful). I was the only one using bash, some others in my year used Ansible. They seemed to be spending half of each afternoon trying to fix something in Ansible, also trying to use other people's scripts if I remember correctly, etc.; for me another preference was just another line of bash and it worked reliably given that the desktops were all the same OS. If you know bash already and you don't want to use it to reinvent a big wheel, yeah I would not hesitate to use it after seeing this struggle with more modern tools. Most of the Docker setup configs I see are already 60% bash commands strung together with backslashes on each line and broken syntax highlighting (because you're in a different file format).

More love needs to go into docker-compose for podman. https://github.com/containers/podman-compose https://github.com/containers/podman-compose

by geenat 5y ago

More love needs to go into docker-compose for podman. https://github.com/containers/podman-compose https://github.com/containers/podman-compose

jordemort 5y ago

I've been using regular old docker-compose with podman since podman 3.2.0. You need to enable the podman socket, which kind of takes away some of the daemonless fun, but once you do that (and point your DOCKER_HOST at the appropriate location), you can "docker-compose up" and it will just work.

ron0c 5y ago

I used to think so until I started just using bash scripts in replacement of docker-compose files.

ageofwant 5y ago
What is your bash depends_on: equivalent ? I like the idea of keeping it simple bash, but seems like it is a step back.
- arve0 5y ago
  I’ve used wait-for-it with success. https://github.com/vishnubob/wait-for-it https://github.com/vishnubob/wait-for-it
- ron0c 5y ago
  I had to look up what depends_on accomplishes, so maybe I'm missing something here, but wouldn't an If/then/else sort that out as well as give you more options?
lucb1e 5y ago
Anecdotally, and perhaps keep in mind I'm quite skilled with bash, in school we had a few people managing their desktops with scripts. Set things like desktop preferences, ssh config, sometimes add a different desktop environment (we each had our own user and it worked with LDAP, so we roamed around and that's why this was useful). I was the only one using bash, some others in my year used Ansible. They seemed to be spending half of each afternoon trying to fix something in Ansible, also trying to use other people's scripts if I remember correctly, etc.; for me another preference was just another line of bash and it worked reliably given that the desktops were all the same OS. If you know bash already and you don't want to use it to reinvent a big wheel, yeah I would not hesitate to use it after seeing this struggle with more modern tools. Most of the Docker setup configs I see are already 60% bash commands strung together with backslashes on each line and broken syntax highlighting (because you're in a different file format).