remote host with hawser agent - "adopt" of existing stacks not possible

[GerLan]

If you try to adopt existing stacks like it is possible since 1.07 on a remote host with working hawser agent it shows only the folders from the main host and not a folder from the remote host.

[jotka]

hi @GerLan

Right now, Dockhand follows a centralized approach for file operations. When you try to adopt, the UI asks the main Dockhand server to list directories.

Even if you select a remote host (via Hawser), the file list currently executed by the Dockhand on its own local filesystem.

The Hawser agent is currently used primarily for Docker API proxying (managing containers), but it doesn't yet have a dedicated file system API exposed to the main server.

That is on the roadmap, but not available today.

[GerLan]

thanks for the update, I compared it to dockge and arcane where this is possible.

[mbhargav294]

It would be great to have this feature!

[Zheltyy]

Just want to point out that Dockhand already has the capability to browse filesystems on remote Hawser hosts - this works perfectly when viewing files inside containers on the remote server through the container file browser.

Since the infrastructure for remote filesystem access via Hawser is already implemented and working (proven by the container file browser), it seems like the "adopt stack" feature just needs to use the same mechanism to browse the remote host filesystem instead of the local Dockhand filesystem.

This would make the feature much more practical for remote host management. Thanks for considering!

[jotka]

Just want to point out that Dockhand already has the capability to browse filesystems on remote Hawser hosts - this works perfectly when viewing files inside containers on the remote server through the container file browser.

hi @Zheltyy yes, this is exactly what we will use :)

[Zheltyy]

Nice, do you maybe also already have a time range when this might be released?

[cmerkle]

Anxiously awaiting this feature! I am torn between Dockhand and Komodo and this is the biggest missing feature of Dockhand to me. I have 4 server running docker compose stacks and I really want to be able to manage them all internally in Dockhand

[drgimpfen]

also waiting for that feature to adopt all my remote stacks into dockhand

[rxunique]

Right now, Dockhand follows a centralized approach for file operations. When you try to adopt, the UI asks the main Dockhand server to list directories.

Even if you select a remote host (via Hawser), the file list currently executed by the Dockhand on its own local filesystem.

@jotka thanks for explaining the road map. Just sharing my 2cents on a use case that you may already aware but not mentioned here

without compose & .env file locally, AI agents would be half blinded in troubleshooting, and limited in capabilities. There are multiple ways around that but not quite as simple as having the files locally.

In my homelab, my first response in troubleshooting is get AI agent to tell me what went wrong, only start digging deeper if AI fails.

[keonramses]

Just checking to see if this feature is still being considered or not, thanks.

[serfriz]

Is this feature still being considered? How about directly SSH into the server (not the containers)?

[jotka]

@serfriz very low priority on the backlog..

[radoeka]

@serfriz Ain't it possible to use sshfs to mount the remote system(s) on your Dockhand server or use git to have tot stack files on multiple systems?

[serfriz]

I guess it's possible, I was just considering moving from Komodo which can can do both (import existing stacks and open a ssh terminal to the remote host). So I prefer to keep it simple with Komodo now. Thanks!