docker / hub-feedback

Feedback and bug reports for the Docker Hub
https://hub.docker.com
234 stars 39 forks source link

Automatic build fails. Error in "/common/highland/utils.py" #457

Closed alpegon closed 3 years ago

alpegon commented 8 years ago

Hi, this error appears when trying to create a docker image using the automated build options:

Encountered error: Traceback (most recent call last): File "/common/highland/utils.py", line 35, in build_update_context yield File "/common/highland/monitor.py", line 137, in monitor if self.build_finished(): File "/common/highland/monitor.py", line 111, in build_finished raise Exception("Non-zero exit code: %r" % exit_code) Exception: Non-zero exit code: 1

dockerhub_error

The dockerfile used is the following https://github.com/grycap/im/blob/tosca/docker-tosca/Dockerfile

Whit previous dockerfiles I had no issues, so I don't know what could be causing this.

Thanks

binhex commented 8 years ago

yep, add me to this issue as well, im seeing the exact same thing on two different repositories now:-

https://hub.docker.com/r/binhex/arch-plexpass/builds/bscpmtf4mbglqzupurecqyq/ https://hub.docker.com/r/binhex/arch-sabnzbd/builds/bxhukaimj4utvgftxlviuma/

davidsketchdeck commented 8 years ago

+1

amuslija commented 8 years ago

+1

hyukim2013 commented 8 years ago

:+1:

flrngel commented 8 years ago

+1

jakirkham commented 8 years ago

Also, seeing this. Builds fine locally. Built fine last week. This occurs every time without fail when running a build that will hit this bug ( https://github.com/docker/hub-feedback/issues/449 ). This bug has cropped up in the last week independently of the submodule bug as I can see submodule build failures 6 days ago when this bug was not present. The first time I see it was 2 days ago. However, I didn't do any builds in that 4 day window so I can't narrow it down any further.

alpegon commented 8 years ago

I have been doing tests all morning and now it's working fine. As final test I used the same Dockerfile and build configuration that was causing the error and it also worked fine. I'm not having this issue anymore, but it seems that some other users are. Check your builds again and if they are working I will close this issue.

jakirkham commented 8 years ago

Sorry @alpegon, this is definitely still an issue for me and I can reliably reproduce it. I strongly recommend this remain open until it is fixed.

alpegon commented 8 years ago

Ok, not a problem

jakirkham commented 8 years ago

Thanks.

jakirkham commented 8 years ago

I created a simple example that reproduces this issue. See the message in this build ( https://hub.docker.com/r/jakirkham/docker_449_test/builds/b4k8sfjqdnypafs8asw7ap9/ ). Screenshot below.

screen shot 2015-11-11 at 11 47 25
shift commented 8 years ago

+1

jakirkham commented 8 years ago

Seeing a variant on this.

screen shot 2015-11-14 at 14 16 38
github-actions[bot] commented 3 years ago

We are clearing up our old issues and your ticket has been open for 6 months with no activity. Remove stale label or comment or this will be closed in 15 days.