From f5b5c1d2c65540871fa2e8f200e45f97eb0ec116 Mon Sep 17 00:00:00 2001
From: Daniel <872187+cyrtified@users.noreply.github.com>
Date: Thu, 25 Mar 2021 17:07:17 +0000
Subject: [PATCH] Update Hugo container image

Update the Hugo container image used for GitLab deployments and provide a link to the container registry.
---
 content/en/hosting-and-deployment/hosting-on-gitlab.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/content/en/hosting-and-deployment/hosting-on-gitlab.md b/content/en/hosting-and-deployment/hosting-on-gitlab.md
index 0a40eb824..6634dbbe7 100644
--- a/content/en/hosting-and-deployment/hosting-on-gitlab.md
+++ b/content/en/hosting-and-deployment/hosting-on-gitlab.md
@@ -38,7 +38,7 @@ cd your-hugo-site
 In the root directory of your Hugo site, create a `.gitlab-ci.yml` file. The `.gitlab-ci.yml` configures the GitLab CI on how to build your page. Simply add the content below.
 
 {{< code file=".gitlab-ci.yml" >}}
-image: monachus/hugo
+image: registry.gitlab.com/pages/hugo:latest
 
 variables:
   GIT_SUBMODULE_STRATEGY: recursive
@@ -53,6 +53,10 @@ pages:
   - master
 {{< /code >}}
 
+{{% note %}}
+All available Hugo versions are listed [here](https://gitlab.com/pages/hugo/container_registry)
+{{% /note %}}
+
 ## Push Your Hugo Website to GitLab
 
 Next, create a new repository on GitLab. It is *not* necessary to make the repository public. In addition, you might want to add `/public` to your .gitignore file, as there is no need to push compiled assets to GitLab or keep your output website in version control.