> Does the ssh transport work with the "more specialized" containers?

It took me a bit to get that set up, but no, it doesn't. Did essentially this:

https://linuxhandbook.com/ssh-into-container/

Created a directory with some files in it in the homedir of the container,
and then added the project with the location as `/ssh:root@localhost#7655:Folder`.
It found the folder just fine (eg showed up in completion), but when I added 

it and did project-find-files, I got the same error as usual.

On Sunday, May 26th, 2024 at 5:26 PM, Dmitry Gutov <dmitry@gutov.dev> wrote:

> On 26/05/2024 20:21, alexis purslane wrote:
> 

> > Actually, no, installing git does not help resolve the problem
> > whatsoever. One works, the other two don't, but I can't tell why. The
> > one that works is my general purpose development container, and the
> > other two are more specialized, so that may be the origin of the
> > problem, but it doesn't explain what in particular is missing. What does
> > project.el rely on the host having installed?
> 

> 

> project-find-file just uses 'git ls-files' if it's in a repository, or
> 'find' otherwise.
> 

> If your file name string juggling made things work correctly, it seems
> unlikely that the problem is in some missing software on the remote host.
> 

> Does the ssh transport work with the "more specialized" containers?