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.
On 8/8/23 14:34, lejeczek via Podman wrote:
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.
_______________________________________________ Podman mailing list --podman@lists.podman.io To unsubscribe send an email topodman-leave@lists.podman.io
podman run --env foo=xyz#bar alpine printenv foo xyz#bar Not much Podman can do about this.
On Tue, Aug 08, 2023 at 08:34:31PM +0200, lejeczek via Podman wrote:
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.
Interesting. Looks like a bug in option parsing. Would you mind filing an issue here? https://github.com/containers/podman/issues/new/choose
I often use # - does anybody have a way to make it work?
A workaround is to define & export in your environment, then use the no-equals form of '-e': $ export foo='abc#defg' $ podman run --env foo <--- Just 'foo', not 'foo=anything' E -- Ed Santiago [he/him] Toolsmith santiago@redhat.com
Hi. I don't remember if I filed a bug report then, I don't think so. I see that this is still an issue - would be great to have it fixed in - should I create a report for it now? thanks, L.
participants (3)
-
Daniel Walsh -
Ed Santiago -
lejeczek