Update within a Docker container
The only way to update an workerinstalled in a container is to remove the previous version and create a new one.
Download new image and remove the old container with the workerusing the command:
docker pull xopero/gitprotect-agent:latest
docker stop xopero-worker&& docker rm xopero-agentAnd now create the new container with agent:
docker run -d \
--name xopero-worker\
-e ManagementServiceUrl="<your_gitprotect_service_URL>" \
-e XoperoOverriddenHostName="<device_name>" \
-v /opt/gitprotect-agent/data:/app/Xopero \
--restart unless-stopped \
xopero/gitprotect-agent:latestThis method requires the Container Station to be at least version 3.0.
First, open Container Station on your QNAP device. Once you have accessed Container Station, locate and select the container running the workerthat you want to update. After selecting the appropriate container, click on the settings icon to access the container settings.
In the settings menu, you will see an option labeled “Recreate”. Click on this option to proceed with the update. This action will allow you to replace the current container with a new one based on the latest image.
Next, you need to configure the settings. Switch to advanced mode, as shown in the illustration provided. In advanced mode, you will be prompted to enter the image address from Docker Hub. Enter the following address:
xopero/gitprotect-agent:latest
Additionally, ensure you check the option “Try pulling the image from the registry before creating the container”. This step is crucial as it ensures you are using the latest version of the image.
After configuring these settings, click "Next" to proceed. At this point, you have the option to edit the container settings as you would when creating a new container. Make any necessary adjustments or simply click "Next" again to proceed to the summary page.
Finally, review the summary of the settings and changes. Once you are satisfied, click "Finish". Container Station will then download the latest image and create a new container using the settings and data from the previous container. This process ensures that your workercontainer is updated to the latest version while preserving all existing settings and data.
By following these steps, you can easily keep your workercontainer up-to-date, ensuring optimal performance and access to the latest features and improvements.
The only way to update an workerinstalled in a container is to remove the previous version and install a new one. Creating a new container requires re-activating the device, so you'll need to re-pin the device to all plans.
Go to the Devices tab and select the Docker agent. Click the Device details button. Check the Docker workerplans and remember to add them again. All Plans can be seen in the Backup plans section, expand the list by clicking Load more.
Remove the old container with the workerGitProtect. Go to the Container station, and click the Remove icon from the Actions tab to delete the old container.
Now, when the old container (which should be updated) is removed, install the GitProtect workerdocker image again. After that, add the workerto all plans where it was included.
When utilizing the :latest tag, the Container Manager actively monitors for updates to the associated image. Upon detecting a new version, a notification will appear in the Image tab, displaying the status "(Update available)". To initiate the update process, simply select the "(Update available)" button.
If you don’t see the Update available button, you have to wait almost 12 hours before you can see the Update available button.
Upon activation, a system prompt will indicate that the services and container will be temporarily suspended during the update procedure. Proceed by confirming with the "Update" button.
A subsequent confirmation step will require the user to reaffirm the update by selecting "Update" once more.
The update progress will be displayed in the list of operations. Once the updated image has been successfully downloaded, containers configured with the Auto-start option will be restarted automatically.
To verify the update, navigate to the Containers tab to ensure proper container functionality. Additionally, in the GitProtect Management Panel, confirm that the system reflects the latest version.
Last updated