-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building with --mount=type=ssh
erroring with error serving agent: read unix /tmp/blah/ssh_auth_sock->@: use of closed network connection
#3587
Comments
@ashley-cui @flouthoc PTAL |
A friendly reminder that this issue had no activity for 30 days. |
Hi, I'm encountering the same issue.. podman 3.4.2 |
@flouthoc @ashley-cui any progress? |
@rhatdan Ackd. Will check this |
@jspc @vulturm You can use |
@flouthoc fair point, but that's not the problem we're seeing, and is why I put the semicolon after the Does your PR mean that agents work as expected now? Because if you look at the original issue body, the connection never even made it as far as github; the agent connection fails, which means the ssh command is unable to load the correct key from the agent, and as such the command fails. It's only evident by using In fact, when I discovered this issue it was trying to |
@jspc Yes PR above PR fixes that. |
Fair enough @flouthoc. I don't get how increasing the sleep duration stops agent connections failing, but I trust your work- and I just tried it myself. Good work! |
@jspc yeah it might look confusing. I have added in the description of the PR but i'll explain again. call to Ideally we should |
OK. It seems a little hacky, but moves us forward. |
seeing the same error when building an image with podman that uses ssh mount from the Dockerfile:
running fedora 36 on WSL and it works if i use docker to build
|
Description
Hello.
When building a container image as per:
$ podman build --ssh default .
From the Dockerfile:
Results in the log line:
(Or, of course, whichever directory
ioutil.TempDir("", ".buildah-ssh-sock")
creates).I've put the
sleep
in there to try and diagnose further:When I run the bottommost command (
SSH_AUTH_SOCK=.buildah-ssh-sock1848960062/ssh_auth_sock ssh [email protected]
) I get the same error message in mypodman build
window:Steps to reproduce the issue:
Dockerfile
to diskpodman build --ssh default .
Describe the results you received:
The error message
use of closed network connection
Describe the results you expected:
Output of
rpm -q buildah
orapt list buildah
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:The text was updated successfully, but these errors were encountered: