Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Getting 413 error when pushing image to docker registry

    Docker Registry
    3
    7
    1701
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      esawtooth last edited by

      I am getting the following error when trying to push my docker image into this registry. Any suggestions on how to fix?

      error parsing HTTP 413 response body: invalid character '<' looking for beginning of value: "<html>\r\n<head><title>413 Request Entity Too Large</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>413 Request Entity Too Large</h1></center>\r\n<hr><center>nginx/1.14.0 (Ubuntu)</center>\r\n</body>\r\n</html>\r\n"
      
      1 Reply Last reply Reply Quote 0
      • M
        msbt App Dev last edited by

        this means you're not on the latest version, there's already a fix for that I believe

        E 1 Reply Last reply Reply Quote 1
        • E
          esawtooth @msbt last edited by

          @msbt Thanks! Looks like I missed the latest update. It's working fine now.

          E 1 Reply Last reply Reply Quote 0
          • E
            esawtooth @esawtooth last edited by

            @msbt I am still getting this error for very large images now, while smaller images seem to get pushed without issues. Is there some associated parameter that controls the size of images that can be pushed?

            girish 1 Reply Last reply Reply Quote 0
            • girish
              girish Staff @esawtooth last edited by

              @esawtooth Can you confirm you are on Cloudron 6.1.2 and also using the docker registry package 1.0.0 ? The entity too large was specifically fixed in package 1.0.0.

              E 1 Reply Last reply Reply Quote 0
              • E
                esawtooth @girish last edited by esawtooth

                @girish Platform version is 6.1.2. Regarding package version, I see it listed as 0.6.0 (Screenshot below)? An update seems be be available, but for some reason, the updated version seems to be 0.5.0, which cannot be "updated" to.
                a6c02026-2e86-46d6-bebe-1121fb5c0e87-image.png

                Clearly, this is not 1.0.0, but am not sure why I am not getting that app update. I updated this app a while ago successfully, but did not note the pkg version I was updating to then I'm afraid.

                E 1 Reply Last reply Reply Quote 0
                • E
                  esawtooth @esawtooth last edited by esawtooth

                  Refreshing the UX a couple of times, got me an available 1.0.0 update. Looks like some weird bug. In any case, I'll make sure my package version is 1.0.0 and check again.

                  Update: This is working now. Tested with a few large images. Thanks!

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Powered by NodeBB