Is there any way to override the storage.conf options?

[ziXet]

I would like to run some podman commands with different options in the storage.conf.

Without this option I need to use "sed" to comment and uncomment specific lines in the storage.conf before and after running my special podman command which is not ideal with multiprocessing.

I'd prefer to run something like this:
podman image pull --storage storage.options.additionalimagestores=["/storage"]

Is it possible?

[giuseppe]

podman --storage-opt...? Is that what you would like to use?

[ziXet]

podman --storage-opt...? Is that what you would like to use?

Thanks for the response.
I would like to override the value of additionalimagestores in the storage.conf. I think --storage-opt is for overriding "storage driver options".

Please correct me if I'm wrong

[giuseppe]

I think you are right. I don't see a way to change the additionalimagestores using --storage-opt.

Anyway, I think that allowing a different additionalimagestores per container could cause some issues. For example how would we find the image referred by the container if the stores can change? We would need to store the configuration per each container

[ziXet]

My use case is a bit special. I would like to pull the images to the additional storage using:
podman image pull myimage:v1 --root /storage
If I run this command while I have additionalstorage=['/storage'] in my storage.conf, I get this error:
Error: lock "/storage/overlay-images/images.lock" is not a read-only lock
To solve this issue, I need to set the additionalstorage=[] or comment it out. after pulling a readonly image, I can put the '/storage' back to the additionalstorage.

[rhatdan]

I am working on a better fix for this, but this will work.

podman image pull myimage:v1 --storage-opt=overlay.mountopt=nodev --root /storage

[ziXet]

I am working on a better fix for this, but this will work.

podman image pull myimage:v1 --storage-opt=overlay.mountopt=nodev --root /storage

Thanks Dan! it actually worked!

[rhatdan]

I have a PR for this, just need to get it merged.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

This is now fixed in master branch.