podman intel mpi container
by ugiwgh＠qq.com
I run podman with intel mpi. But there is something wrong.
Any help will be appreciated.
--GHui
$ mpirun --version
Intel(R) MPI Library for Linux* OS, Version 2021.5 Build 20211102 (id: 9279b7d62)
Copyright 2003-2021, Intel Corporation.
$ mpirun -np 2 podman run --env-host --env-file envfile --network=host --pid=host --ipc=host -w /exports -v .:/exports:z centos/ /exports/mpitest
[cli_0]: write_line error; fd=9 buf=:cmd=init pmi_version=1 pmi_subversion=1
:
system msg for write_line failure : Bad file descriptor
[cli_0]: Unable to write to PMI_fd
[cli_0]: write_line error; fd=9 buf=:cmd=get_appnum
:
system msg for write_line failure : Bad file descriptor
Abort(1090575) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack:
MPIR_Init_thread(143):
MPID_Init(1221)......:
MPIR_pmi_init(130)...: PMI_Get_appnum returned -1
[cli_0]: write_line error; fd=9 buf=:cmd=abort exitcode=1090575
:
system msg for write_line failure : Bad file descriptor
Attempting to use an MPI routine before initializing MPICH
[cli_1]: write_line error; fd=10 buf=:cmd=init pmi_version=1 pmi_subversion=1
:
system msg for write_line failure : Bad file descriptor
[cli_1]: Unable to write to PMI_fd
[cli_1]: write_line error; fd=10 buf=:cmd=get_appnum
:
system msg for write_line failure : Bad file descriptor
Abort(1090575) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack:
MPIR_Init_thread(143):
MPID_Init(1221)......:
MPIR_pmi_init(130)...: PMI_Get_appnum returned -1
[cli_1]: write_line error; fd=10 buf=:cmd=abort exitcode=1090575
:
system msg for write_line failure : Bad file descriptor
Attempting to use an MPI routine before initializing MPICH
^C[mpiexec(a)ja0909.para.bscc] Sending Ctrl-C to processes as requested
[mpiexec(a)ja0909.para.bscc] Press Ctrl-C again to force abort
3 years
podman traceback with env var a=b=c
by Barry Scott
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.
Barry
3 years
Re: Need help in creating a rootless container in podman
by Anton Peters
Now that is remarkable. The overlay subdir has a supposedly random unique number.
Me and my colleagues get exactly the same as a SHA256 hash for a duplicate blob when trying to push an image to quay.io :
Getting image source signatures
Error: trying to reuse blob sha256:476579af086aee78cb12d88b08fd6b61a80a3f055cae293ec2d15a37dbe7b3f9 at destination: Requesting bearer token: invalid status code from registry 400 (Bad Request)
This must be something deep in how container images are handled.
I wonder what data generates this specific hash; maybe an empty data set?
--
Anton Peters
3 years
oscap-podman as non root
by Ed Haynes
In RHEL9 I installed oscap-podman script as part of the openscap-utils
package. I'd like to use this script to scan container images pulled by a
non-root user but when running says I have to run as root - any idea why
this is a hard dependency? If I do have to run script as root is there
any way to pass non root podman image ID to the script?
Thanks, Ed
--
Ed Haynes
Senior SOLUTIONS ARCHITECT
Red Hat <https://www.redhat.com/>
ehaynes(a)redhat.com *M: (978)-551-0057 *
TRIED. TESTED. TRUSTED.
3 years, 1 month
Podman Community Meeting - Tues, June 7, 2022, at 11:00 a.m. EDT (UTC-5)
by Tom Sweeney
Hi All,
The next Podman Community Meeting is happening this Tuesday, June 7,
2022, @ 11:00a.m. EDT(UTC-5). We'll be having a new demo on the new
Desktop, what is being planned for the next few releases, and more! In
fact, we've room for another topic or two, so if you have one that you'd
like to present or discuss, drop me a line.
Free to attend here: https://bluejeans.com/880216278/2568
t
3 years, 1 month
