Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Podman v6.0.0

blog.podman.io

Post reply on HN
Print view View original

261–269 of 269 posts

Re: Podman v6.0.0

#261

Post by rsyring »

thayne wrote: post #249
rsyring wrote: post #165

Earlier quoted context omitted.

I run Ubuntu 24.04 on my laptop and servers. The Podman version is 4.9.3. It may be incompressible to you, but I'm not alone in thinking it's a problem: https://github.com/podman-container-tools/podman/issues/2707...

If you use an LTS version of Ubuntu (or Red Hat etc.), you are going to have older versions of software. That's just how it works. And is kind of the point of LTS. If you want more recent versions, use a rolling release or a more recent (non-LTS) version of Ubuntu (or whatever). The latest version of podman is going to depend on recent versions of the kernel and systemd, etc. and isn't going to work well on an older…

There's a perfectly legit reason for wanting a stable, non-rolling, OS while keeping some software updated beyond versions the OS provides.

Lots of other software providers seem to care about being compatible with LTS releases of popular distros, like...Docker! They seem to manage supporting the older kernel and systemd versions just fine.

And, my entire argument here, is that this difference between Podman and Docker is glaring and one of the reasons Podman isn't more popular.

Re: Podman v6.0.0

#262

Post by rsyring »

YorickPeterse wrote: post #233
rsyring wrote: post #165

Earlier quoted context omitted.

I run Ubuntu 24.04 on my laptop and servers. The Podman version is 4.9.3. It may be incompressible to you, but I'm not alone in thinking it's a problem: https://github.com/podman-container-tools/podman/issues/2707...

You're running an LTS release first released in 2024. What exactly did you expect was going to happen?

See my comment at https://news.ycombinator.com/item?id=48785731

Re: Podman v6.0.0

#263

Post by rsyring »

globular-toast wrote: post #189
rsyring wrote: post #165

Earlier quoted context omitted.

I run Ubuntu 24.04 on my laptop and servers. The Podman version is 4.9.3. It may be incompressible to you, but I'm not alone in thinking it's a problem: https://github.com/podman-container-tools/podman/issues/2707...

That's a you problem. Either use a rolling distro like Gentoo or Arch or learn to install software from source code yourself (it's not hard).

See my comment at: https://news.ycombinator.com/item?id=48785731

Re: Podman v6.0.0

#264

Post by ijustlovemath »

teekert wrote: post #220
ijustlovemath wrote: post #117

Earlier quoted context omitted.

what kind of stuff is in your compose?

Mostly self made containers, also one with Claude-code, but I couldn't for the life of me get it to be able to store and retrieve credentials in an externally mounted folder (~/.claude). I tried everything from fixing the user creation process in the container, `--userns=keep-id`, `--userns=keep-id:uid=1000,gid=1000`, several tags, :Z, :U, `chown`-ing after creation etc. And I keep running into that stuff. I wish tha…

I had to do some extra stuff for my containers, here's some info from a tutorial I wrote:

Following the Arch wiki:

# Dependencies `yay -S podman slirp4netns aardvark-dns`

# Setup podman-compose and the venv ``` python -m venv .venv source .venv/bin/activate pip3 install --user podman-compose ```

On WSL, you'll need to be on Debian bookworm or newer. Older versions of podman-compose for, ie, bullseye, do not work.

# Reserving alternate UIDs/GIDs `# usermod --add-subuids 100000-165535 --add-subgids 100000-165535 username`

# Setup the storage configuration to overlay Create/edit the following file: `vim ~/.config/containers/storage.conf`

Add/edit the following line: ``` [storage] driver="overlay" ```

# Propagate changes to podman `$ podman system migrate`

# Bring the systems up `podman-compose up`

# I'm on WSL and it's not working (DNS issues)

Check if the network created by podman has dns enabled:

``` % podman network inspect $containername_default | grep dns "dns_enabled": true, ```

If it's false, install another dns resolver:

``` sudo apt install golang-github-containernetworking-plugin-dnsname ```

Then delete the network created by podman-compose:

`podman network rm $containername_default`

## Out of memory when running `podman-compose up`

This error may include "could not map anonymous shared memory".

If you're on a mac, try increasing the amount of memory the VM can use, eg:

https://stackoverflow.com/questions/70114200/increase-podman...

``` podman machine stop podman machine set --memory 4096 podman machine start ```

This will provide podman with 4GB of memory to work with when spawning containers.

https://gist.github.com/ijustlovemath/82b4fa31a7c745e87bac5f...

Re: Podman v6.0.0

#265

Post by teekert »

ijustlovemath wrote: post #264
teekert wrote: post #220

Earlier quoted context omitted.

Mostly self made containers, also one with Claude-code, but I couldn't for the life of me get it to be able to store and retrieve credentials in an externally mounted folder (~/.claude). I tried everything from fixing the user creation process in the container, `--userns=keep-id`, `--userns=keep-id:uid=1000,gid=1000`, several tags, :Z, :U, `chown`-ing after creation etc. And I keep running into that stuff. I wish tha…

I had to do some extra stuff for my containers, here's some info from a tutorial I wrote: Following the Arch wiki: # Dependencies `yay -S podman slirp4netns aardvark-dns` # Setup podman-compose and the venv ``` python -m venv .venv source .venv/bin/activate pip3 install --user podman-compose ``` On WSL, you'll need to be on Debian bookworm or newer. Older versions of podman-compose for, ie, bullseye, do not work. # R…

Thanx!

It's a lot of stuff to set up though, compared to disaster recovery instructions being: Install Docker, restore state from x, docker compose up -d.

I want it all "as code", this could certainly be automated (scripts, nix), but it would be nice if it really was as simple as one single compose file, that should be the goal, imho.

Re: Podman v6.0.0

#266

Post by michaelmrose »

smarx007 wrote: post #256
rsyring wrote: post #152

Earlier quoted context omitted.

Agreed. But, IMO, it looks like amateur hour when you compare their stance to the distro support Docker provides.

A slightly different perspective: Podman is made by the distro people (RedHat/Fedora). And they consider it unacceptable to mess with the software distribution channels of a distro. If Debian does not want latest Podman, they are not going to push the latest version to Debian users behind Debian repo's "back". This is a distro-to-distro respect rather than amateur hour.

I do not think this perspective is correct. You are considering official distro repos as a means to control what is allowed to be run on Debian. This is a kind of control commercial platforms often value because they use it to extract rent or to micromanage their experience that they sell to the rubes.

Debian DOES care about about both experience and ethics of what is allowed to be distributed in official repos but it is contrary to the ethos of free software to care what you run on your machine or by extension what others choose to offer. You are intuiting a corporate sort of perspective where neither it nor the raison d'être for it exists.

Re: Podman v6.0.0

#267

Post by smarx007 »

michaelmrose wrote: post #266
smarx007 wrote: post #256

Earlier quoted context omitted.

A slightly different perspective: Podman is made by the distro people (RedHat/Fedora). And they consider it unacceptable to mess with the software distribution channels of a distro. If Debian does not want latest Podman, they are not going to push the latest version to Debian users behind Debian repo's "back". This is a distro-to-distro respect rather than amateur hour.

I do not think this perspective is correct. You are considering official distro repos as a means to control what is allowed to be run on Debian. This is a kind of control commercial platforms often value because they use it to extract rent or to micromanage their experience that they sell to the rubes. Debian DOES care about about both experience and ethics of what is allowed to be distributed in official repos but i…

> You are considering official distro repos as a means to control what is allowed to be run on Debian.

I am rather considering official repos as a means to keeping your Debian system in a "supported" state. Many users, including software developers, want to only install software (or sw versions) that would not put their system in an unsupported configuration.

> Debian DOES care about about both experience and ethics of what is allowed to be distributed in official repos

Podman is widely distributed in official Debian repos, so ethics is not a question in this particular case. We are only talking about Debian repos being conservative with the versions of the software in the repos - not limited to Podman. Debian does not encourage users to install software from 3rd-party repos just to get a newer version of an existing package because the stability of the system (and the ability to do major version upgrades) cannot be guaranteed otherwise.

Re: Podman v6.0.0

#268

Post by ijustlovemath »

teekert wrote: post #265
ijustlovemath wrote: post #264

Earlier quoted context omitted.

I had to do some extra stuff for my containers, here's some info from a tutorial I wrote: Following the Arch wiki: # Dependencies `yay -S podman slirp4netns aardvark-dns` # Setup podman-compose and the venv ``` python -m venv .venv source .venv/bin/activate pip3 install --user podman-compose ``` On WSL, you'll need to be on Debian bookworm or newer. Older versions of podman-compose for, ie, bullseye, do not work. # R…

Thanx! It's a lot of stuff to set up though, compared to disaster recovery instructions being: Install Docker, restore state from x, docker compose up -d. I want it all "as code", this could certainly be automated (scripts, nix), but it would be nice if it really was as simple as one single compose file, that should be the goal, imho.

To be clear, all of that setup happens once on your host machine, then you never have to think about it again! You can compose to your heart's content. I think podman just doesn't want to commit to a particular DNS solution so they leave that decision to you.
Post reply on HN