Hugo: Docker image auto build and deploy

[kfeofantov]

Please, add automated docker build and push at docker hub in CI Pipeline.
I can write pipeline for CircleCI or Travis.

[mlake]

+1 for Composeability

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[Yajo]

I think this is still relevant because Hugo users usually perform some kinda autobuild for their websites, usually done in a CI/CD pipeline, usually based on Docker for easiness and reusability.

This would make the project more usable, and still more maintainable because CI would do the dirty job.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[jonahbron]

I would also like to see an officially maintained Docker image be added. :+1:

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[eugene-bright]

There is an official docker image on dockerhub. But it is stale like this issue.

[bep]

There is an official docker image on dockerhub. But it is stale like this issue.

That gohugoio account isn't official.

[eugene-bright]

So it's a well crafted fake that drains reputation then.

[pierreozoux]

Gitlab provides one.
I also think that the project should provide one, it would be cleaner for our CICD pipelines :)
If you need help to set it up, please don't hesitate to ask!

[jufemaiz]

Let’s get this moving on dockerhub?

[ChenXiyu]

It is a good practice to wrap a command line tool into a docker image, I believe.
Could you please release an official image for us?

I know it's easy to build image for ourselves, but It need every individual who use Hugo as docker containers to watch Hugo releases to keep updated. If we got an official docker image, Dependabot could help to update our image tags.

Or you have other concerns about this?
Is the dockerhub account name bothering?

[peaceiris]

We (I) plan to use GitHub to publish docker images.

https://github.com/gohugoio/hugo/pull/6405#issuecomment-548280568

FYI.

https://github.com/gohugoio/hugo/issues/5056 is a similar issue.

[Christoph-Harms]

How can one help with this? Sure, if people want to use hugo in their automated, containerized environments, they can just clone the repo and do the docker build themselves. But it is pretty much standard to provide a dockerized version of a CLI application. It's the direction the industry has been moving in for the past years.

When I tried to use the gohugoio/hugo image last week and noticed that it is based upon a version of hugo that is two years old, I was very confused. Then I noticed that it is not THIS repo that the image is built upon, but a fork. So I thought: "Alright, some 2 years ago, someone broke the docker build. And apparently it was very hard to fix or something. So they switched to a working fork, and then forgot it or deprioritized it or whatever." So I thought, I'm going to fork the hugo repo and fix the damn build, do something for the OS community.

I was even more confused when I cloned my fork, ran docker build on it and everything worked. I don't understand. Docker Hub has an autobuild feature. Providing an up-to-date docker image should be as easy as re-connecting THIS repo to the gohugoio/hugo repo on Docker Hub and telling it to auto-build everytime something gets merged into master. But then again, if it was that easy, it would have been done, right? So what am I missing?

[bep]

@Christoph-Harms I recommend this one: https://hub.docker.com/r/klakegg/hugo/

[Christoph-Harms]

That gohugoio account isn't official.

I overlooked that comment of yours, @bep. That explains it. Shame that it "looks" official, because the account names on Docker Hub and Github are the same. :/ It gives a taste of, I don't know, unreliability? It's not exactly what I mean, but I don't have a better word. It puts hugo in a bad light. Kind of. I hope what I want to say here actually comes across. 😅 I love hugo and I want everyone else to love it, too! :)

@Christoph-Harms I recommend this one: https://hub.docker.com/r/klakegg/hugo/

Looks great, thank you! I didn't even find that one when browsing Docker Hub. Only old forks or specialized builds.

[bep]

@Christoph-Harms @klakegg is reliable. I understand that the "official Hugo docker situation" isn't ... ideal, but it's a priority/time thing. I have now added the klakegg Docker to the Hugo install page so it should be easier to find.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.