Closed
Description
Preliminary checklist
- I am using the latest stable version of DDEV (see upgrade guide)
- I have searched existing issues
- I have checked the troubleshooting guide
- I have run
ddev debug testto include output below
Output of ddev debug test
Not debug test but I don't think that's useful in this case anyways!
❯ docker run --rm ddev/ddev-webserver-prod:v1.24.3 which git
/usr/bin/git
❯ docker run --rm ddev/ddev-webserver-prod:v1.24.3 which ssh
exit status 1
❯ docker run --rm ddev/ddev-webserver-prod:v1.24.0 which ssh
/usr/bin/ssh
Expected Behavior
ssh is available so git can work.
Actual Behavior
Cloning into '/tmp/tmp.JkH5ATrbRF'...
error: cannot run ssh: No such file or directory
fatal: unable to fork
Cloning into '/tmp/tmp.JkH5ATrbRF'...
error: cannot run ssh: No such file or directory
fatal: unable to fork
Steps To Reproduce
- Turn on hardened images (in our case, we're using
ddev config global --use-hardened-imagesin CI as it's a faster download). - Try to do git clone with an SSH remote. In our case, we need that to be able to pull a repository down from Pantheon and then later push back up to it.
Anything else?
#6839 (review) suggested removing both git and ssh, but in practice git was left in. It seems like either:
- git should be removed, because it is not that useful without ssh.
- ssh should be added back in.
- Even if nothing changes, can we update the release notes? It wasn't clear from me scanning them that the above PR touched the hardened images - I only figured it out by running
git log -S -p sshlocally.
Metadata
Metadata
Assignees
Labels
No labels