This question extends my last question about 'How to comply with the GPL when providing auto updates'.
I want to distribute a Debian VM with Debian based docker containers, so far I would just extract the entire source code after the VM is configured and provide the source code on a physical medium e.g. USB-Stick and thus complying with the GPL by providing the source code alongside the binary.
The problem is that some of my smaller customers don't want to update the VM themselves.
This poses the question on how to update the debian VM and the docker containers for my customer without constantly having to provide the source code for the updated version. (I do not want to manage all the different source code versions, so I want to deliver the source code once and then the customer or some tool should to the updates)
If I provide an admin tool that let's the customer update the Debian VM and the Debian based docker containers from public repositories e.g the official Debian repository and docker hub for the base containers, would it then be enough to give my customer only the source code for the delivered GPL programs within the Debian vm and containers on an USB drive to comply with the various GPL licenses ?
Could this tool also be automated e.g. with a cron job ?
Let's say my customer pays me again to do the updates as a service for him manually e.g accessing his server because he hired me to update the software, am I correct in assuming that this would not count as distribution because I act on behalf of my customer and only use public repositories (default debian ftp to update debian and docker hub plus my docker scripts to update the containers)?