3 ms·

I second that. It's a definite flaw in marketing and mid-term planning. curl | sh is a bad practice, but lack of "curl https://get.docker.com https://get.docker

I second that. It's a definite flaw in marketing and mid-term planning. curl | sh is a bad practice, but lack of "curl https://get.docker.com https://get.docker.com | sh" scenario is certainly bad for Podman adoption. For some reason Docker Desktop users on macOS and Windows are prioritized over non-rpm Linux users. (OTOH, there are some technical blockers as well, such as AppArmor support. Podman development team is obviously more accustomed with SELinux and expect some external contributions in that field)

acdha 3y ago
Why do you think Linux users aren’t prioritized? This supports every Linux distribution I’ve ever needed to use an a few others besides: https://podman.io/docs/installation https://podman.io/docs/installation
- throwaway74354 3y ago
  Official guide regarding Ubuntu or Debian will get you podman 3.4.4 in case if Ubuntu 22.04 or 4.3.1 in case of Debian 12. The project is in active development with lots of re-architecturing, deprecations and security fixes. There has to be a way to obtain relatively updated binary packages while not being tied to distribution update cadence. There's still https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/ https://download.opensuse.org/repositories/devel:/kubic:/lib... , but it's not what one could consider production ready. Example of why: https://github.com/containers/podman/issues/5102#issuecomment-737600718 https://github.com/containers/podman/issues/5102#issuecommen...
  - acdha 3y ago
    Oh, that’s not a Podman issue - the Debian world is like RHEL I’m being conservative about major version upgrades. They’re still shipping Python 3.10 and 3.11, too, despite 3.12 having been released and 3.13 waiting in the wings. The build from source instructions work and you can easily maintain your own back ports / PPAs for things like that as the standard mechanism for major upgrades which the core distribution doesn’t want to commit to supporting. Usually you can simply take the updated package definition from the unstable repository and build that, and a quick search suggests many people are doing just that.

acdha 3y ago

Why do you think Linux users aren’t prioritized? This supports every Linux distribution I’ve ever needed to use an a few others besides: https://podman.io/docs/installation https://podman.io/docs/installation

throwaway74354 3y ago
Official guide regarding Ubuntu or Debian will get you podman 3.4.4 in case if Ubuntu 22.04 or 4.3.1 in case of Debian 12. The project is in active development with lots of re-architecturing, deprecations and security fixes. There has to be a way to obtain relatively updated binary packages while not being tied to distribution update cadence. There's still https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/ https://download.opensuse.org/repositories/devel:/kubic:/lib... , but it's not what one could consider production ready. Example of why: https://github.com/containers/podman/issues/5102#issuecomment-737600718 https://github.com/containers/podman/issues/5102#issuecommen...
- acdha 3y ago
  Oh, that’s not a Podman issue - the Debian world is like RHEL I’m being conservative about major version upgrades. They’re still shipping Python 3.10 and 3.11, too, despite 3.12 having been released and 3.13 waiting in the wings. The build from source instructions work and you can easily maintain your own back ports / PPAs for things like that as the standard mechanism for major upgrades which the core distribution doesn’t want to commit to supporting. Usually you can simply take the updated package definition from the unstable repository and build that, and a quick search suggests many people are doing just that.