You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used to install the urbackup client on the actual host, but I am trying to do it through a container now. I am putting the client on the same compose stack as the server, using the proper mounts, and a network between the two.
The server is seeing the clients, and the backups works. Everything works, really, except the fact that every time the stack is destroyed and recreated, the client uses a new, random-generated name, therefore, I end up with endless backups of the same thing:
Thank you for your input. If you have a PR for the solution, I'm happy to look at that, otherwise I'll do some investigation on my own when I get the time.
I used to install the urbackup client on the actual host, but I am trying to do it through a container now. I am putting the client on the same compose stack as the server, using the proper mounts, and a network between the two.
The server is seeing the clients, and the backups works. Everything works, really, except the fact that every time the stack is destroyed and recreated, the client uses a new, random-generated name, therefore, I end up with endless backups of the same thing:
Here is my docker-compose:
As you can see, there is no need to declare the ports for the client, because it is in the same default network as the client.
It would be great if it could actually use the same name/identifier, even after recreate.
The text was updated successfully, but these errors were encountered: