podman: e2e: sign image: Unexpected error: can't connect to the gpg-agent
podman sign image
...
Unexpected error:
<*exec.ExitError | 0xc0019f86c0>:
exit status 2
{
ProcessState: {
pid: 130096,
status: 512,
rusage: {
Utime: {Sec: 0, Usec: 6129},
Stime: {Sec: 0, Usec: 10342},
Maxrss: 62000,
Ixrss: 0,
Idrss: 0,
Isrss: 0,
Minflt: 603,
Majflt: 5,
Nswap: 0,
Inblock: 520,
Oublock: 56,
Msgsnd: 0,
Msgrcv: 0,
Nsignals: 0,
Nvcsw: 34,
Nivcsw: 15,
},
},
Stderr: nil,
}
the ginkgo line seems to be https://github.com/containers/podman/blob/a91cde637ee2b4f6e8db60147b2f46e6fe482476/test/e2e/image_sign_test.go#L48-L50
There’s no useful output or any indication of what the error actually is, but I’m going to guess that this is another contention bug which needs to be addressed either via locking or via $GNUPGHOME or --homedir
Podman image sign [It] podman sign image
- fedora-37 : int podman fedora-37 rootless host sqlite
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 15 (6 by maintainers)
Commits related to this issue
- test/e2e: gpg keep stdout/err attached By default go will not keep the stdout/err attach when executing commands via exec.Command(). It is required to explicitly pass the current stdout/err fds down ... — committed to Luap99/libpod by Luap99 a year ago
- e2e: serialize gpg tests Reason: gpg tests all run with a different GNUPGHOME, and gpg-agent does not like that, and there's no longer any way to run gpg without the agent. So, do not run these tests... — committed to edsantiago/libpod by edsantiago a year ago
- e2e: serialize gpg tests Reason: gpg tests all run with a different GNUPGHOME, and gpg-agent does not like that, and there's no longer any way to run gpg without the agent. So, do not run these tests... — committed to edsantiago/libpod by edsantiago a year ago
- e2e: serialize gpg tests Reason: gpg tests all run with a different GNUPGHOME, and gpg-agent does not like that, and there's no longer any way to run gpg without the agent. So, do not run these tests... — committed to edsantiago/libpod by edsantiago a year ago
- e2e: serialize gpg tests Reason: gpg tests all run with a different GNUPGHOME, and gpg-agent does not like that, and there's no longer any way to run gpg without the agent. So, do not run these tests... — committed to edsantiago/libpod by edsantiago a year ago
- e2e: serialize gpg tests Reason: gpg tests all run with a different GNUPGHOME, and gpg-agent does not like that, and there's no longer any way to run gpg without the agent. So, do not run these tests... — committed to edsantiago/libpod by edsantiago a year ago
For the record, https://github.com/containers/image/pull/1779 includes a way to kill the agent.