Text of forums.docker.com › t › autobuild-doesnt-work › 99349 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Autobuild doesn't work - Docker Hub - Docker Community Forums

Autobuild doesn't work Docker Hub automatedbuilds dokervirus (Dokervirus) October 6, 2020, 4:46am 1 My repo is here: https://hub.docker.com/repository/docker/dokervirus/archlinux_dev/builds I have connected it to my github repo too: https://github.com/bpangWR/archlinux_dev_container and configured my docker hub repo for Automated Builds. But it just doesn’t work: It would not automatically trigger a build whenever I made a push, and it also still doesn’t work when I click the “trigger” button.

Any idea why this happens? and is there a place I can check what’s the problem in my REPO? Thanks, Baoshan michaelgosselin (Michaelgosselin) October 14, 2020, 1:04am 2 I’m having some similar issues. Issue type BUILD OS Version/build Windows 10 1909 / 18363 App version 2.4.0.0 Steps to reproduce Following docker online tutorial. PS C:\WINDOWS\system32\doodle\cheers2019> docker run -it --rm michaelgosselin/cheers2019 Unable to find image ‘michaelgosselin/cheers2019:latest’ locally docker: Error response from daemon: manifest for michaelgosselin/cheers2019:latest not found: manifest unknown: manifest unknown.

See ‘docker run --help’. PS C:\WINDOWS\system32\doodle\cheers2019> jonathanrrogers (Jonathan Rogers) October 29, 2020, 6:45am 3 I had exactly the same problem. I created a new repository on GitHub, then a new repository on Docker Hub and connected the GitHub repository to it with the default build rule. I couldn’t get a build to trigger at all, even by manually clicking the “Trigger” button. After staring at the GitHub repository for a while, I realized it had been created with default branch “main”, ignoring the conventional “master”.

I fixed the problem by creating a branch called “master” in my GitHub repository. Most of the blame lies with GitHub for violating a convention which had been in place since the creation of git. If some people want to change the default branch name for their new repositories, GitHub should enable that. I didn’t make such a choice and wasted time because of the extremely surprising change that I had neither been aware of nor consented to.

Some blame also lies with Docker Hub for giving no feedback about the misconfiguration. It looked for a branch named “master” and didn’t find one, then did absolutely nothing. Why notify the user that such a branch doesn’t exist? Related topics Topic Replies Views Activity Automated build never builds! Docker Hub docker , build 17 10940 May 27, 2022 Unable to trigger docker build via rest api or web UI Docker Hub 12 918 January 7, 2023 Automated Build from GitHub Not Triggering Docker Hub automatedbuilds 3 1934 June 2, 2016 Automated build not picking up changes in github repo Docker Hub 12 5890 August 18, 2016 Autobuild Not Triggering Docker Hub automatedbuilds 0 561 May 11, 2022