| Description |
This article describes the troubleshooting process when a scheduled backup of FortiPortal does not work due to no access to download docker images. |
| Scope | FortiPortal v7.x. |
| Solution |
Most users deploy FortiPortal without any access to the internet except for FortiGuard for license validation. In such deployments, the scheduled backup of FortiPortal may not work due to a dependency on docker images for curl. There is no error logged in the system logs as well.
Below are the steps to identify and troubleshoot this issue.
From the FortPortal CLI, run the command 'execute list-container':
From the output above, the cronjob for backup is PodInitializing. Run the command 'execute detail-container' to display the details of each container. The reason for the cronjob to be in PodInitializing is a dependency container image for curl images.
Below is the snippet of the error:
Failed to pull image "curlimages/curl": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/curlimages/curl:latest": failed to resolve reference "docker.io/curlimages/curl:latest": failed to do request: Head "https://registry-1.docker.io/v2/curlimages/curl/manifests/latest": dial tcp 44.208.254.194:443: i/o timeout
The error suggests that FortiPortal is trying to download the 'curl' container image from the docker repository but has failed. The scheduled backup operation will fail due to this dependency issue.
Enable access to docker.io for the FortiPortal to download this 'curl' container image. After the download is complete, the scheduled backup works as expected. The access to docker.io can be revoked after the operation as it is a one-time download to the FortiPortal. |
