Hi Barry,
Thanks for reaching out and for tracking down the issue.
On Tue, Jun 14, 2022 at 3:51 PM Barry Scott <barry.scott(a)forcepoint.com>
wrote:
I ran a build that works with docker and hit a traceback with a
simple fix.
I symlinked docker and docker-compose to podman and podman-compose.
There is env var that is of the form A=B=C which needs this patch to allow
podman-compose to work:
$ diff -u /usr/lib/python3.10/site-packages/podman_compose.py~
/usr/lib/python3.10/site-packages/podman_compose.py
--- /usr/lib/python3.10/site-packages/podman_compose.py~ 2022-06-14
14:16:45.825406742 +0100
+++ /usr/lib/python3.10/site-packages/podman_compose.py 2022-06-14
14:16:45.825406742 +0100
@@ -1502,7 +1502,7 @@
if args.workdir: cnt["working_dir"] = args.workdir
env = dict(cnt.get('environment', {}))
if args.env:
- additional_env_vars = dict(map(lambda each: each.split('='),
args.env))
+ additional_env_vars = dict(map(lambda each: each.split('=', 1),
args.env))
env.update(additional_env_vars)
cnt['environment'] = env
if not args.service_ports:
With this fix the build worked as expected.
Let me know if you want this in a bugzilla.
If you are a Red Hat customer, please open a bug there. You may also open
an issue on GitHub.
Kind regards,
Valentin
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io