[Podman] Re: Announcement: New Podman pre-release - v4.7.0-rc1
by Tom Sweeney
> means of stitching Podman instances across machines together on the
roadmap?
Not that I know of at this point, but just in case I'm not thinking
about the right thing, could you expound a little bit more on what
"stiching Podman instances" would mean in your thinking?
t
On 9/15/23 19:22, Neal Gompa wrote:
> On Fri, Sep 15, 2023 at 7:15 PM Lokesh Mandvekar
> <lsm5(a)fedoraproject.org> wrote:
>
> Happy late Friday all,
>
> Podman v4.7.0-rc1 is now available.
>
> v4.7.0-rc1 brings two shiny new commands:
> 1. `podman farm` to "farm" out builds to machines running Podman
> for different architectures.
> 2. `podman compose` as a thin wrapper around an external compose
> provider such as docker-compose or podman-compose.
>
> along with a host of enhancements to `podman kube`, support for
> more Quadlet fields, and lots of bugfixes.
>
> Check out the release page for a full list of features, changes
> and bugfixes.
> https://github.com/containers/podman/releases/tag/v4.7.0-rc1
>
> Enjoy!
>
>
> Congratulations on the new release! I'm looking forward to this!
> Question though: is there some means of stitching Podman instances
> across machines together on the roadmap?
>
> It seems like you're halfway there with the podman farm...
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
> _______________________________________________
> Podman mailing list --podman(a)lists.podman.io
> To unsubscribe send an email topodman-leave(a)lists.podman.io
1 year, 8 months
[Podman] Re: Wordpress container running on mac cannot create theme directory on mounted path
by Mehdi Haghgoo
Hi Johannes, Thanks for the idea. I tried using absolute path in docker-compose.yaml, but it fails to launch the container with "Permission Denied" error saying that it cannot mkdir /Users. This is strange because the /Users directory should already exist on Podman machine. This is not an issue on fedora by the way when I run docker-compose.
Any ideas?
On Fri, Jun 16, 2023 at 9:35, Johannes Kastl<kastl(a)b1-systems.de> wrote: On 02.06.23 at 19:22 Mehdi Haghgoo via Podman wrote:
> volumes:
> - .:/var/www/html
I guess this is no typo, you are really using "." as volume for /var/www/html?
> volumes:
> wp_uploads: {}
> wpdb_vol: {}
> When running the containers, in WordPress admin page, I cannot install a plugin. Basically, the container is not allowed to create directories under wp-content. It fails with permission error:
> "Could not create directory /var/www/html/wp-content/upgrade/oceanwp-3.4.4/oceanwp"
>
> I tried chmod 777 on all wp-content (with -r), but it didn't help.
I would try using a "real volume" (and not just ".") for /var/www/html.
My guess would be that due to MacOS and Podman Machine (and not using Podman
directly, like on Linux) this does not work.
Kind Regards,
Johannes
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: kastl(a)b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg
http://www.b1-systems.de
GF: Ralph Dehner
Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
1 year, 11 months
[Podman] Re: HELP! recover files from a deleted container
by Alvin Thompson
Thanks. I have a call to my company’s IT department hoping they made a recent backup (not likely), but if that doesn’t work I’ll try that.
Thanks,
Alvin
> On Sep 4, 2023, at 2:32 PM, Robin Lee Powell <rlpowell(a)digitalkingdom.org> wrote:
>
> If you have the image, and you know what the data you're looking for
> looks like (i.e. it's text you can search for), try just loading the
> image in a hex editor and searching for it.
>
> On Mon, Sep 04, 2023 at 09:05:37AM -0400, Alvin Thompson wrote:
>> Hi and thanks for the suggestions,
>>
>> Since this is Podman for Windows which uses a WSL instance, I’m hopeful that not starting Podman or messing within the WSL instance will preserve the data if necessary. WSL stores the EXT4 filesystem in a vhdx image which hopefully is isolated from Windows enough. If I’m wrong about this please let me know.
>>
>> This is a work computer with rather strict controls so what I can do with it is limited. I did make a copy of the WSL disk image so that’s something. Unfortunately, I may have already overwritten the data because in a panic the first thing I did was try to copy any folder I could find with the name “container”. I was hoping the files would be unlinked and cleaned up later if space were needed. Perhaps that’s a feature suggestion.
>>
>> I’ll see if I can grab another Intel computer, install VirtualBox on it, attach a copy of the image, and boot a recovery DVD with that.
>>
>> Thanks,
>> Alvin
>>
>>
>>> On Sep 4, 2023, at 8:15 AM, Tobias Wendorff <tobias.wendorff(a)tu-dortmund.de> wrote:
>>>
>>> 1. Immediately stop using the system: Cease all activities and avoid any further operations on the affected system. This minimizes the risk of overwriting the data you want to recover.
>>>
>>> 2. Turn it off as soon as possible. Maybe unplug the power supply to turn it off immeditely.
>>>
>>> 3. Don't boot from the disk again. Remove it if necessaray.
>>>
>>> 4. Boot into a data-recovery DVD or put it on another system and mount it read-only.
>>>
>>> The more you do on the hard drive, the more likely it is that the data will be overwritten. The data is then virtually unrecoverable. Normally, however, you can recover deleted data. They were not intentionally overwritten (shredded).
>>>
>>>
>>> Am 04.09.2023 um 12:26 schrieb Alvin Thompson:
>>>> Help!
>>>> Is there any way to recover files from a deleted container? Long story short, I found the behavior of `podman network rm -f` unexpected, and it wound up deleting most of my containers. One in particular had a month of work in it (I was using it as a development environment), and it turns out only part of it was backed up. I’m desperate!
>>>> This is Podman for Windows, so most of the files on the “host” are in the WSL environment. I can get into that no problem with `wsl -d podman-machine-default`.
>>>> As an added wrinkle, my default connection was `podman-machine-default-root`, but I was was not running Podman rootful. I’m not sure this is particularly relevant.
>>>> grep-ing for strings which are unique to the development environment shows one hit in Windows, in %HOME%/.local/containers/podman/machine/wsl/wsldist/podman-machine-default/ext4.vhdx - which I assume is the file system for the WSL layer itself. I made a copy of it.
>>>> A grep within WSL itself doesn’t show so any hits, so it’s possible the files were deleted as far as WSL is concerned. I tried searching for an EXT4 undelete tool, but the only one I found (extundelete) is from 10+ years ago and doesn’t appear to work anymore.
>>>> I haven’t stopped WSL (I’m using /tmp as a staging area) or restarted the computer.
>>>> I’m at wit’s end. I really don’t know where to begin or look to recover these files, which I really, really need. Any recovery suggestions (no matter how tedious) would be welcome.
>>>> I know it’s too late to change now, but man, the behavior of `podman network remove` is unexpected.
>>>> Thanks,
>>>> Alvin
>>>> _______________________________________________
>>>> Podman mailing list -- podman(a)lists.podman.io
>>>> To unsubscribe send an email to podman-leave(a)lists.podman.io
>> _______________________________________________
>> Podman mailing list -- podman(a)lists.podman.io
>> To unsubscribe send an email to podman-leave(a)lists.podman.io
1 year, 8 months
[Podman] Re: Use host proxy inside container
by Daniel Walsh
On 2/4/23 14:53, Mehdi Haghgoo wrote:
> Daniel I looked up some SOCKS protocol
> information(https://www.rfc-editor.org/rfc/rfc1928) and there is no
> explicit mention of using a socket file to make the connection. I have
> no idea how it would be possible to use SOCKS with Podman.
It does not look like Podman would directly support SOCKS.
> By the way, does Podman or Podman Desktop support using a HTTP proxy
> like Minikube does?
>
Yes you can set the HTTP Proxy environment files and podman will use them.
>
> On Saturday, February 4, 2023 at 02:42:45 AM GMT+3:30, Daniel Walsh
> <dwalsh(a)redhat.com> wrote:
>
>
> On 2/3/23 16:33, Mehdi Haghgoo via Podman wrote:
> Hello,
>
> I need to use a network proxy running with socks as
> socks5://127.0.0.1:1090 on my host system, inside the container
> running with podman.
>
> How can I tell Podman to use that proxy inside the container as well?
> Does Podman support this?
>
>
>
> _______________________________________________
> Podman mailing list --podman(a)lists.podman.io <mailto:podman@lists.podman.io>
> To unsubscribe send an email topodman-leave(a)lists.podman.io <mailto:podman-leave@lists.podman.io>
>
> I am not that familiar with socks, does it create a socket file to
> communicate with? If so then this socket can be volume mounted into
> the container and be used, although you will probaly need to disable
> SELinux separation.
>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
2 years, 3 months
[Podman] Re: Rootless container startup failure at bootup, launches fine manually
by jklaiho＠iki.fi
The IP firewall warning seems to be unrelated. On another server where we didn't get this problem on a reboot, the same warning is emitted for one of the several rootless containers running there. It's interesting on its own, and I found where it happens in the systemd code here:
https://github.com/systemd/systemd/blob/e30b4c13570a5e4ec794d480d5371e9c7...
...but that seems like another, likely benign issue with rootless Podman and systemd/cgroups, maybe?
The later errors seem to be the actual failure here, but I don't know what to make of them.
- JK
> On Thursday, May 25, 2023 at 7:21 PM, Chris Evich <cevich(a)redhat.com (mailto:cevich@redhat.com)> wrote:
> On 5/25/23 08:03, jklaiho(a)iki.fi wrote:
> > systemd[746]: cms_backend.service: unit configures an IP firewall, but not running as root.
> > systemd[746]: (This warning is only shown for the first unit using IP firewalling.)
>
> I'm not an expert, but to my untrained eye, this message seems to be the
> root-cause indicator. I can't say for sure where/why that error is
> generated but it seems like it could be some kind of bug in quadlet
> interactions w/ the rest of systemd. Maybe try changing the
> dependencies (Wants/After) might make a difference? That's a total
> guess though.
>
> ---
> Chris Evich (he/him), RHCA III
> Senior Quality Assurance Engineer
> If it ain't broke, your hammer isn't wide 'nough.
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
2 years
[Podman] Re: Follow-up: Rootless storage usage
by Reinhard Tartler
On Tue, Jan 24, 2023 at 2:08 PM Daniel Walsh <dwalsh(a)redhat.com> wrote:
> On 1/24/23 03:47, Reinhard Tartler wrote:
>
> Dan,
>
> In Debian, I've chosen to just go with the upstream defaults:
> https://github.com/containers/storage/blob/8428fad6d0d3
> c4cded8fd7702af36a09f02b858f/storage.conf#L116-L118
>
> This file is installed verbatim to /usr/share/containers/storage.conf.
>
> Is there a better choice? Does Fedora/Redhat provide a default
> storage.conf from somewhere else?
>
>
> Thanks,
> -rt
>
> That should be fine. Fedora goes with that default as well. Does debian
> support rootless overlay by default?
>
> If not then it would fail over to VFS if fuse-overlayfs is not installed.
>
I'm a bit confused about what you mean with that.
In Debian releases that ship podman 4.x we have at least Linux kernel 6.0.
The fuse-overlayfs package is installed by default, but users may opt to
not install it by configuring apt to not install "Recommends" by default.
What else is required for rootless overlay?
Also, if I follow this conversation, then it appears that the default
storage.conf requires modification in line 118 (to uncomment the
mount_program option) in order to actually use fuse-overlayfs. I would have
expected podman to use fuse-overlayfs if it happens to be installed, and
fallback to direct mount if not. I read Michail's email thread that this
appears to be not the case and he had to spend a lot of effort figuring out
how to install an appropriate configuration file. Maybe I'm missing
something, but I wonder what we can do to improve the user experience?
-rt
--
regards,
Reinhard
2 years, 4 months
[Podman] Re: Can user override registries.conf?
by Valentin Rothberg
On Fri, Sep 22, 2023 at 9:01 PM Rahaman, Ronald O <rrahaman6(a)gatech.edu>
wrote:
> Hi all,
>
>
>
> Can you confirm that, in rootless, users cannot override
> /etc/containers/registries.conf with ~/.config/containers/registries.conf
> ? We’d like to be able to whitelist registries for our site.
>
Yes, users can override system configurations in their home directory. As
outlined in the man pages [1], the config in the home directory will be
loaded _instead_ of the system configuration in /etc. That means it will
override and not add to the system configuration.
Kind regards,
Valentin
[1]
https://github.com/containers/image/blob/main/docs/containers-registries....
> As an example, suppose I have this in /etc/containers/registries.conf.
> The intent is to blacklist all of docker.io; and whitelilst
> docker.io/ubuntu. I’ve found it works as intended.
>
>
>
> [[registry]]
>
> location="docker.io"
>
> blocked=true
>
>
>
> [[registry]]
>
> location="docker.io/ubuntu"
>
> blocked=false
>
>
>
> I want to confirm that a user can’t whitelist additional registries in
> ~/.config/containers/registries.conf with something like
>
>
>
> [[registry]]
>
> location="docker.io/unsafe-namespace"
>
> blocked=false
>
>
>
> I’ve tested this myself, and it seems like users can’t override. But I’d
> like to be 100% sure.
>
>
>
> Thanks,
>
> Ron
>
>
>
> --------
>
> Ron Rahaman
>
> Research Scientist II, Research Software Engineer
>
> Partnership for an Advanced Computing Environment (PACE)
>
> Georgia Institute of Technology
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
1 year, 8 months
[Podman] Re: HELP! recover files from a deleted container
by Alvin Thompson
Yep, when I’m working on my Mac I do that. Working from Windows is a little more problematic since it doesn’t have unix-like file permissions. I’m not sure if Podman works around that somehow—does it? I guess I could have tried to map the volume to somewhere in the WSL install (if possible). Live and learn.
-Alvin
> On Sep 4, 2023, at 12:05 PM, Александр Илюшкин <ailjushkin(a)gmail.com> wrote:
>
> Hey, Alvin.
>
> Sorry to read about that. But anyways I'm glad that you've lost only your personal work, not a production one.
>
> > One in particular had a month of work in it (I was using it as a development environment), and it turns out only part of it was backed up. I’m desperate!
>
> It was painful but good experience to remember that the main idea of containers consists in stateless approach. In general, there is no guarantees that your container and its data will be available for a long time, but there is a guarantee that it can be quickly started up again, scaled to a number of instances.
>
> So, if you work under container environment, you have to store your data outside, whether it's a database, or a file storage.
>
> С уважением, А. И.
>
> пн, 4 сент. 2023 г., 13:27 Alvin Thompson <alvin(a)thompsonlogic.com <mailto:alvin@thompsonlogic.com>>:
>> Help!
>>
>> Is there any way to recover files from a deleted container? Long story short, I found the behavior of `podman network rm -f` unexpected, and it wound up deleting most of my containers. One in particular had a month of work in it (I was using it as a development environment), and it turns out only part of it was backed up. I’m desperate!
>>
>> This is Podman for Windows, so most of the files on the “host” are in the WSL environment. I can get into that no problem with `wsl -d podman-machine-default`.
>>
>> As an added wrinkle, my default connection was `podman-machine-default-root`, but I was was not running Podman rootful. I’m not sure this is particularly relevant.
>>
>> grep-ing for strings which are unique to the development environment shows one hit in Windows, in %HOME%/.local/containers/podman/machine/wsl/wsldist/podman-machine-default/ext4.vhdx - which I assume is the file system for the WSL layer itself. I made a copy of it.
>>
>> A grep within WSL itself doesn’t show so any hits, so it’s possible the files were deleted as far as WSL is concerned. I tried searching for an EXT4 undelete tool, but the only one I found (extundelete) is from 10+ years ago and doesn’t appear to work anymore.
>>
>> I haven’t stopped WSL (I’m using /tmp as a staging area) or restarted the computer.
>>
>> I’m at wit’s end. I really don’t know where to begin or look to recover these files, which I really, really need. Any recovery suggestions (no matter how tedious) would be welcome.
>>
>> I know it’s too late to change now, but man, the behavior of `podman network remove` is unexpected.
>>
>> Thanks,
>> Alvin
>> _______________________________________________
>> Podman mailing list -- podman(a)lists.podman.io <mailto:podman@lists.podman.io>
>> To unsubscribe send an email to podman-leave(a)lists.podman.io <mailto:podman-leave@lists.podman.io>
1 year, 8 months
[Podman] Re: Reliable service starts
by Valentin Rothberg
Hi Mark,
Thanks for reaching out.
I suggest using `podman generate systemd` to generate a systemd unit.
There's also a new way of running Podman inside of systemd called Quadlet
that ships with the just released Podman v4.4. A blog about that topic is
in the pipeline.
Given the complexity of running Podman in systemd, `podman generate
systemd` and Quadlet are the only supported ways.
In your case, I suggest removing `podman pull` from the service. In
contrast to `podman pull`, `podman run` won't redundantly pull the image if
it's already in the local storage. That will relax the network bottleneck.
Kind regards,
Valentin
On Thu, Feb 2, 2023 at 10:00 PM Mark Raynsford via Podman <
podman(a)lists.podman.io> wrote:
> Hello!
>
> I'm using podman on Fedora CoreOS. The standard setup for a
> podman-based service tends to look like this (according to the
> documentation):
>
> ---
> [Unit]
> Description=looseleaf
> After=network-online.target
> Wants=network-online.target
>
> [Service]
> Type=exec
> TimeoutStartSec=60
> User=_looseleaf
> Group=_looseleaf
> Restart=on-failure
> RestartSec=10s
>
> Environment="_JAVA_OPTIONS=-XX:+UseSerialGC -Xmx64m -Xms64m"
>
> ExecStartPre=-/bin/podman kill looseleaf
> ExecStartPre=-/bin/podman rm looseleaf
> ExecStartPre=/bin/podman pull docker.io/io7m/looseleaf:0.0.4
>
> ExecStart=/bin/podman run \
> --name looseleaf \
> --volume /var/storage/looseleaf/etc:/looseleaf/etc:Z,ro \
> --volume /var/storage/looseleaf/var:/looseleaf/var:Z,rw \
> --publish 20000:20000/tcp \
> --memory=128m \
> --memory-reservation=80m \
> docker.io/io7m/looseleaf:{{looseleaf_version}}
> <http://docker.io/io7m/looseleaf:%7B%7Blooseleaf_version%7D%7D> \
> /looseleaf/bin/looseleaf server --file /looseleaf/etc/config.json
>
> ExecStop=/bin/podman stop looseleaf
>
> [Install]
> WantedBy=multi-user.target
> ---
>
> The important line is this one:
>
> /bin/podman pull docker.io/io7m/looseleaf:0.0.4
>
> Unfortunately, this line can fail. That in itself isn't a problem, the
> service will be restarted and it'll run again. The real problem is that
> it can fail in ways that will break all subsequent executions.
>
> On new Fedora CoreOS deployments, there's often a lot of network
> traffic happening on first boot as the rest of the system updates
> itself, and it's not unusual for `podman pull` to fail and leave the
> services permanently broken (unless someone goes in and fixes them).
>
> This is what will typically happen:
>
> Feb 02 20:31:05 control1.io7m.com podman[1934]: Trying to pull
> docker.io/io7m/looseleaf:0.0.4...
> Feb 02 20:31:48 control1.io7m.com podman[1934]:
> time="2023-02-02T20:31:48Z" level=warning msg="Failed, retrying in 1s ...
> (1/3). Error: initializing source docker://io7m/looseleaf:0.0.4: pinging
> container registry registry-1.docker.io: Get \"https://regist>
> Feb 02 20:31:50 control1.io7m.com podman[1934]: Getting image source
> signatures
> Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob
> sha256:9794579c486abc6811cea048073584c869db02a4d9b615eeaa1d29e9c75738b9
> Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob
> sha256:8921db27df2831fa6eaa85321205a2470c669b855f3ec95d5a3c2b46de0442c9
> Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob
> sha256:846e3b32ee5a149e3ccb99051cdb52e96e11488293cdf72ee88168c88dd335c7
> Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob
> sha256:7f516ed68e97f9655d26ae3312c2aeede3dfda2dd3d19d2f9c9c118027543e87
> Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob
> sha256:e88daf71a034bed777eda8657762faad07639a9e27c7afb719b9a117946d1b8a
> Feb 02 20:32:03 control1.io7m.com systemd[1]: looseleaf.service:
> start-pre operation timed out. Terminating.
>
> It'll usually happen again on the next service restart. Then, this will
> tend to happen:
>
> Feb 02 20:34:13 control1.io7m.com podman[2745]:
> time="2023-02-02T20:34:13Z" level=error msg="Image
> docker.io/io7m/looseleaf:0.0.4 exists in local storage but may be
> corrupted (remove the image to resolve the issue): size for layer
> \"13cfed814d5b083572142bc>
> Feb 02 20:34:13 control1.io7m.com podman[2745]: Trying to pull
> docker.io/io7m/looseleaf:0.0.4...
> Feb 02 20:34:14 control1.io7m.com podman[2745]: Getting image source
> signatures
> Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob
> sha256:9794579c486abc6811cea048073584c869db02a4d9b615eeaa1d29e9c75738b9
> Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob
> sha256:8921db27df2831fa6eaa85321205a2470c669b855f3ec95d5a3c2b46de0442c9
> Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob
> sha256:846e3b32ee5a149e3ccb99051cdb52e96e11488293cdf72ee88168c88dd335c7
> Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob
> sha256:7f516ed68e97f9655d26ae3312c2aeede3dfda2dd3d19d2f9c9c118027543e87
> Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob
> sha256:e88daf71a034bed777eda8657762faad07639a9e27c7afb719b9a117946d1b8a
> Feb 02 20:34:18 control1.io7m.com podman[2745]: Copying config
> sha256:cce9701f3b6e34e3fc26332da58edcba85bbf4f625bdb5f508805d2fa5e62e3e
> Feb 02 20:34:18 control1.io7m.com podman[2745]: Writing manifest to image
> destination
> Feb 02 20:34:18 control1.io7m.com podman[2745]: Storing signatures
> Feb 02 20:34:18 control1.io7m.com podman[2745]: Error: checking platform
> of image cce9701f3b6e34e3fc26332da58edcba85bbf4f625bdb5f508805d2fa5e62e3e:
> inspecting image: size for layer
> "13cfed814d5b083572142bc068ae7f890f323258135f0cffe87b04cb62c3742e" is unkno>
> Feb 02 20:34:18 control1.io7m.com systemd[1]: looseleaf.service: Control
> process exited, code=exited, status=125/n/a
>
> At this point, there's really nothing that can be done aside from
> having a human log in and running something like "podman system reset".
>
> These systems are supposed to be as immutable as possible, and
> deployments are supposed to be automated. As it stands currently, I
> can't actually a deploy a machine and not have it immediately break and
> require a manual intervention.
>
> Is there some better way to handle this?
>
> --
> Mark Raynsford | https://www.io7m.com
>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
2 years, 3 months
[Podman] Re: Follow-up: Rootless storage usage
by Daniel Walsh
On 1/24/23 03:47, Reinhard Tartler wrote:
>
>
> On Tue, Jan 3, 2023 at 10:27 AM Daniel Walsh <dwalsh(a)redhat.com> wrote:
>
> On 12/30/22 08:35, Михаил Иванов wrote:
>> > You could do a podman system reset and then remove all content
>> > from the storage with
>> > rm -rf ~/.local/share/containers
>> > To make sure there is nothing hidden there,
>> But that's almost exactly what I did:
>> > I just purged the whole storage using podman system reset.
>> > I verified that ~/.local/share/containers became empty
>> > (only bolt database was still remaining using about 200Mb space)
>>
>> I'm using whatever storage was provided by default podman install
>> (debian sid/bookworm) podman is 4.3.1 How can I reconfigure it to
>> different type? I assumed this has to be done in storage.conf but
>> this file is not present anywhere at all.
> I have no idea why debian would be choosing VFS, unless this is an
> older version of debian and did not support rootless overaly. You
> could try installling fuse-overlayfs and doing another reset, then
> Podman info should show you using overlay with fuse-overlayfs.
>
>
> Dan,
>
> In Debian, I've chosen to just go with the upstream defaults:
> https://github.com/containers/storage/blob/8428fad6d0d3c4cded8fd7702af36a...
>
> This file is installed verbatim to /usr/share/containers/storage.conf.
>
> Is there a better choice? Does Fedora/Redhat provide a default
> storage.conf from somewhere else?
>
>
> Thanks,
> -rt
>
That should be fine. Fedora goes with that default as well. Does debian
support rootless overlay by default?
If not then it would fail over to VFS if fuse-overlayfs is not installed.
2 years, 4 months