Backups - local stacks, remote host

[Sc0th]

Hi folks,

I have a dockhand host (control) that has stack files locally, they are stored under directory path such as /dockhand_data/stacks/container01/mystackname.

/dockhand_data is mounted into dockhand under /app/data.

I only use direct connection, and I push the stacks to start on remote hosts, e.g container01. I only use bind mounts on the remote hosts, no volumes as it's cleaner for my config.

So when I fire up a stack from dockhand on the 'control' server the compose.yaml never exists on the remote host, not do I want it to.

All this works perfectly for me. However when I try to run a backup I get 'No stack folder found on the host' and I am unable to run backups. Am I missing a step or is my config just not suited to use backups?

Many thanks!

Sc0t

[Sc0th]

Looks like this may be a bug, have raised bug ticket #1442

[jiriteach]

Has this been fixed? I see it's 1.0.44? I'm running the latest 1.0.46 and am experiencing this.

I have all my stacks locally on my Dockhand instances but a ton of docker hosts connected via Docker API.

Backing up via containers is ok.

Backing up via stacks keeps telling me the stack does not exist.
I would like to backup via stacks as I have some stacks on some remote hosts that deploys multiple containers at one time.

Any know how to handle this?

Thanks

[jotka]

@jiriteach needs some logs when you try to start a backup, please.

[jotka]

@jiriteach check what you have configured here on the env:

[jiriteach]

Have tried both the host path /app/data/stacks/machinename using what's mapped.
Tried with the host path actual /home/administrator/Docker/dockhand/stacks/machinename

Doesn't worth

And a path on the remote node

Don't work either.

Could it be because I am connecting via the Docker API?

[jiriteach]

@jotka - Thanks. Here is some additional information. Let me know if there is any other information required or why this could be happening please.

Dockhand is running locally on a docker host and all my stacks are locally on the same host that Dockhand is running on.

I have an additional environment setup on Dockhand which uses a connection type of direct connection.
I have set the remote backup location which is an empty directory since the stack is local to Dockhand.

I then create a backup of a stack for testing -

This then fails -

Here is what the logs from Dockhand looks like -

[jotka]

hey @jiriteach is /home/ubuntu/Docker/dockhand/cf-tunnel present on the DOOBER host?

[jiriteach]

It wasnt - I did create that directory path but it didn’t make any difference. I will try it again.

DOOBER - a docker host
/home/ubuntu/Docker/dockhand/cf-tunnel

This is a blank directory - nothing in there since all stacks are on the main dockhand server.

DOCKHAND Server - a docker host
/home/administrator/Docker/dockhand/cf-tunnel/cf-tunnel.yml

It's also mapped via a volume /app/data/stacks/dockhandserver/cf-tunnel/cf-tunnel.yml

[jotka]

That empty directory is the missing piece - but you don't create it by hand. Dockhand copies the stack's files into <Remote stack path>/<stack> on the remote host during a deploy, and only when Remote stack path is set. Creating the folder yourself leaves it empty, so the probe (which looks for cf-tunnel.yml inside it) still fails.

So, on the DOOBER env, with Remote stack path = /home/ubuntu/Docker/dockhand set: redeploy the cf-tunnel stack once (Deploy / Save & redeploy). That stages cf-tunnel.yml (and its config) onto DOOBER at /home/ubuntu/Docker/dockhand/cf-tunnel/. After that, ls /home/ubuntu/Docker/dockhand/cf-tunnel/ on DOOBER should show the compose file, and the backup will find it.

down/start/restart don't re-copy - it has to be a deploy (up). Give that a try and let us know if the file lands.

[jiriteach]

Awesome - thank you!

That works - yes the missing piece was manually creating it by hand. Also important looks like the down/start. Assuming any changes to the stack will be picked up as it will auto run a down/start and that redeploys the yml to the remote side. Thanks again!