I’m trying to setup a CI system with Jenkins that will register a new project on a successful build. The project itself has all the required files, and if I do docker build inside of the project, it will have no issues whatsoever building the image.
Now, I want to user rancher-compose in order to build my docker image through the S3 provider. I actually have some projects, and one of them can actually create the image without any issues. Here’s the log of a successfully created image with rancher-compose
time="2015-12-18T19:28:28Z" level=info msg="Uploading build for employee-cwc-io using provider S3"
time="2015-12-18T19:28:28Z" level=debug msg="Skipping excluded path: node_modules"
time="2015-12-18T19:28:28Z" level=debug msg="Skipping excluded path: node_modules"
time="2015-12-18T19:28:30Z" level=info msg="Build for employee-cwc-io available at https://XXXXXXXX?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=XXXXXXXXX%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20151218T192336Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=2e38746920f00aeb839131ea978c6054"
time="2015-12-18T19:28:30Z" level=debug msg="Comparing hashes for employee-cwc-io: old: digest.ServiceHash{Service:\"62178d86a29abcf8beff1a755159eac7ad9684d9\", LaunchConfig:\"0835e0c8d403daa73c9596929b680e275f232319\", SecondaryLaunchConfigs:map[string]string{}} new: digest.ServiceHash{Service:\"62178d86a29abcf8beff1a755159eac7ad9684d9\", LaunchConfig:\"33f65c563b1ebe1a383f63a9195abcb50c87b49e\", SecondaryLaunchConfigs:map[string]string(nil)}"
time="2015-12-18T19:28:30Z" level=warning msg="Service employee-cwc-io is out of sync with local configuration file"
time="2015-12-18T19:29:24Z" level=info msg="[1/1] [employee-cwc-io]: Started "
time="2015-12-18T19:29:24Z" level=info msg="Project [default]: Project started "
[ssh-agent] Stopped.
In the other hand, I have the same configuration (Dockerfile, docker-compose.yml) in other project, and it fails without providing many explanations:
time="2015-12-18T19:22:33Z" level=info msg="Uploading build for digerati using provider S3"
time="2015-12-18T19:22:55Z" level=info msg="Creating bucket default-81cf494e211a"
time="2015-12-18T19:23:36Z" level=info msg="Build for digerati available at" https://XXXXXXXX?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=XXXXXXXXX%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20151218T192336Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=2e38746920f00aeb839131ea978c6054
time="2015-12-18T19:23:36Z" level=debug msg="Comparing hashes for digerati: old: digest.ServiceHash{Service:\"4f46f236f5b5cd32e73c3a0713d2506f77413dbb\", LaunchConfig:\"be4209ad1da2715286bfe550a9f6db447c5841a4\", SecondaryLaunchConfigs:map[string]string{}} new: digest.ServiceHash{Service:\"4f46f236f5b5cd32e73c3a0713d2506f77413dbb\", LaunchConfig:\"089481f0d9fd0cd3854a2c01b41b0c3e16e62ebc\", SecondaryLaunchConfigs:map[string]string(nil)}"
time="2015-12-18T19:23:36Z" level=info msg="Checking for digerati-569b335751f7 on b-i-e-node-001..."
time="2015-12-18T19:23:36Z" level=info msg="Checking for digerati-569b335751f7 on a-i-e-node-001..."
time="2015-12-18T19:23:38Z" level=info msg="Checking for digerati-569b335751f7 on b-i-e-node-001: 4dbd8819-565a-434e-838a-59732a33c4e3 : 404 Client Error: Not Found (\"could not find image: no such id: digerati-569b335751f7:latest\")"
time="2015-12-18T19:23:38Z" level=info msg="Checking for digerati-569b335751f7 on a-i-e-node-001: ee21928e-6594-4284-8299-2521332eb9c9 : 404 Client Error: Not Found (\"could not find image: no such id: digerati-569b335751f7:latest\")"
time="2015-12-18T19:23:38Z" level=error msg="Failed Starting digerati : Pull failed on one of the hosts"
time="2015-12-18T19:23:38Z" level=error msg="Failed to start: digerati : Pull failed on one of the hosts"
time="2015-12-18T19:23:38Z" level=fatal msg="Pull failed on one of the hosts"
Build step 'Execute shell' marked build as failure
[ssh-agent] Stopped.
Here’s the docker-compose.yml of both files (only difference is name):
employee-cwc-io:
build: .
labels:
io.rancher.scheduler.global: 'true'
io.rancher.container.pull_image: always
tty: true
stdin_open: true
Any idea what could it be? Why one project fails, and the other succeeds? Any pointers would be appreciated, thanks!