Getting 413 error when pushing image to docker registry
-
wrote on Feb 9, 2021, 1:55 PM 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" -
@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?
@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.
-
@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.
wrote on Feb 9, 2021, 5:44 PM last edited by esawtooth Feb 9, 2021, 5:46 PM@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.
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.
-
@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.
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.
wrote on Feb 9, 2021, 5:50 PM last edited by esawtooth Feb 9, 2021, 7:14 PMRefreshing 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!
