# in environment ?
by lejeczek
Hi guys.
Do you use # in your envs?
I wonder if it's just me having issues with those.
For a test, to reproduce the issue, 'ghost' web solution
would be easy & quick:
-> $ podman run -dt ...................... --env
database__client=mysql --env
database__connection__host=11.1.0.1 --env
database__connection__user=ghostadm --env
database__connection__password='xyz#admghost' --env
database__connection__database=ghost_xyz --env
url=https://ghost.xyz
So far all I've tried with 'database__connection__password'
failed, quoting &| escaping.
I often use # - does anybody have a way to make it work?
many thanks, L.
3 months
RunRoot & mistaken IDs
by lejeczek
Hi guys.
I experience this:
-> $ podman images
WARN[0000] RunRoot is pointing to a path
(/run/user/1007/containers) which is not writable. Most
likely podman will fail.
Error: creating events dirs: mkdir /run/user/1007:
permission denied
-> $ id
uid=2001(podmania) gid=2001(podmania) groups=2001(podmania)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
I think it might have something to do with the fact that I
changed UID for the user, but why would this be?
How troubleshoot & fix it, ideally without system reboot?
many thanks, L.
4 months, 1 week
shouldn't the current directory be the default context for "podman build"?
by Robert P. J. Day
"man podman-build" suggests that the context argument is optional:
SYNOPSIS
podman build [options] [context]
podman image build [options] [context]
...
If no context directory is specified, then Podman will assume
the current working directory as the build context, which
should contain the Containerfile.
but if i have a directory with nothing but a Containerfile, i get:
$ podman build
Error: no context directory specified, and no containerfile specified
$
OTOH, specifying context of current directory:
$ podman build .
STEP 1: FROM alpine:latest
... etc etc ...
thoughts?
rday
11 months
Two new container images available
by Chris Evich
Two new automated container image builds are now available:
* For Podman, Buildah, and Skopeo: "immutable" tags are being added
to all "stable" images. These tags will never be overwritten,
though they may be removed if a major security/safety
issue is detected. In contrast to the other stable tags, which are
overwritten daily, these images assume you desire to manage any
update vs stability risk. The new tags apply to all combinations
of the semantic tool version, so vX-immutable, vX.Y-immutable, and
vX.Y.Z-immutable will be available.
* quay.io/containers/aio:latest and quay.io/containers/aio:<date stamp>
images contain all three tools (Podman, Buildah, and Skopeo).
The images are built weekly using a fedora-minimal base to keep the
size as small as possible. These are intended as a base-image for
development and/or CI/CD use. The <date stamp> is formatted to be
used as a semantic version. Old tags expire and will be removed
after 1-year.
Please direct any issues, discussions, or RFEs toward the
https://github.com/containers/image_build repo.
1 year, 6 months
podmansh
by Felix Niederwanger
Hello,
I'm trying to get podmansh to work in such a way, that every user has a persistent container.
I've followed the steps of https://docs.podman.io/en/latest/markdown/podmansh.1.html, resulting in a nice setup, where at user login every user get's its own container. Unfortunately the container for the user session is ephemeral, meaning after logging out or system reboot the container is destroyed.
I would like to have a setup, where quadlet setups a base container, but then every user can install their own software and environment, which lasts.
Here is the quadlet file I'm currently using:
```
# /etc/containers/systemd/users/podmansh.container
[Unit]
Description=podmansh container
After=local-fs.target
ExecStartPre=-/bin/mkdir -p %h/data
[Container]
Image=registry.fedoraproject.org/fedora
ContainerName=podmansh
HostName=arctic-fox
RemapUsers=keep-id
RunInit=yes
User=0
Volume=%h/data:%h:Z
WorkingDir=%h
Exec=sleep infinity
[Service]
ExecStartPre=/usr/bin/mkdir -p %h/data
[Install]
RequiredBy=default.target
```
Anyone an idea how to achieve persistent podmansh containers?
Greetings,
phoenix
1 year, 6 months
Re: Podlet Migration Questions
by Paul Nettleton
Thanks!
If publishing the podlet container to quay.io/containers is a no-go, another option is to publish it to the GitHub Packages Container registry, so it would be available at ghcr.io/containers/podlet.
Ok so I'll move the current contribution docs (building and CI stuff) from the README.md to CONTRIBUTING.md and add information about DCO sign-off.
--
Paul Nettleton
k9(a)k9withabone.dev
On Thursday, April 25, 2024 09:23 CDT, Brent Baude <bbaude(a)redhat.com> wrote:
Paul, I'm happy to help you with the GH things. Your asks seem reasonable to me. I'll talk with the team about the quay.io/containers stuff but I don't believe we have given folks access to that before; so there is no precedent. Of the core containers repositories, we do require DCO signoff and will generally fail the PR if it is not included. If you are indifferent about it, my preference would be to require it. On Thu, Apr 25, 2024 at 9:20 AM Paul Nettleton via Podman <podman(a)lists.podman.io> wrote:Hello everyone!
I'm not sure if this is the best place to ask, but I have a few questions regarding finalizing the migration of podlet to the containers org.
I would like to create a "podlet-maintainers" team so that I can add it as an owner of podlet on crates.io. This would allow anyone on the team to publish new versions, improving the bus factor. Is it ok for me to do this? I asked about it on the migration issue, but didn't receive a reply.
I was thinking that it would make sense to move the podlet container image from quay.io/k9withabone/podlet to the quay.io/containers org. What would be the process for getting that started?
It seems that I have lost some privileges in the transfer of the podlet repo as I can no longer access the repository settings, including setting secrets for use in CI. I will probably need to be able to update those if quay.io/containers/podlet is created. Would it be possible to give me the "maintain" role for the podlet repo?
I noticed on my PR for switching compose libraries that a check for commit sign off was added. Is this a requirement for all repositories in the containers org? I don't mind having to sign off commits, but a CONTRIBUTING.md file should be added to the podlet repo explaining this if it is required.
Thanks for your time,
Paul / k9withabone
--
Paul Nettleton
k9(a)k9withabone.dev _______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
1 year, 6 months
Podlet Migration Questions
by Paul Nettleton
Hello everyone!
I'm not sure if this is the best place to ask, but I have a few questions regarding finalizing the migration of podlet to the containers org.
I would like to create a "podlet-maintainers" team so that I can add it as an owner of podlet on crates.io. This would allow anyone on the team to publish new versions, improving the bus factor. Is it ok for me to do this? I asked about it on the migration issue, but didn't receive a reply.
I was thinking that it would make sense to move the podlet container image from quay.io/k9withabone/podlet to the quay.io/containers org. What would be the process for getting that started?
It seems that I have lost some privileges in the transfer of the podlet repo as I can no longer access the repository settings, including setting secrets for use in CI. I will probably need to be able to update those if quay.io/containers/podlet is created. Would it be possible to give me the "maintain" role for the podlet repo?
I noticed on my PR for switching compose libraries that a check for commit sign off was added. Is this a requirement for all repositories in the containers org? I don't mind having to sign off commits, but a CONTRIBUTING.md file should be added to the podlet repo explaining this if it is required.
Thanks for your time,
Paul / k9withabone
--
Paul Nettleton
k9(a)k9withabone.dev
1 year, 6 months
Podman EOL /EOS
by Cody Currens
Hello All,
I was wondering if you could help me find any documentation showing which versions of Podman are no longer supported or considered End of life or support. I checked the github blogs and some mentioned only the current version is however I’d like to be sure before forcing an upgrade. Thanks.
Best Regards,
Cody C
1 year, 7 months
