Regression in upstream sinopia Docker container

Created a new issue to track the following.

Hoping you could help me out @5id, I’m trying to set the tests up on Travis but am running into some trouble with what I think might be the sinopia stuff.

I have a failing build output here https://travis-ci.org/JamieMason/shrinkpack/builds/147702971 – could you take a look for me please?

Thanks.

– JamieMason https://github.com/JamieMason/shrinkpack/pull/47#issuecomment-235532761

---

The changes are in fe6a652

– JamieMason https://github.com/JamieMason/shrinkpack/pull/47#issuecomment-235532940

---

It’s not Travis actually, I’m having the same issues locally where the sinopia server can’t be hit;

npm info attempt registry request try #1 at 3:45:46 PM
npm http request PUT http://secure_registry:4873/-/user/org.couchdb.user:shrinkpack
npm info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND secure_registry secure_registry:4873

I’m using these versions of docker;

$ docker -v
Docker version 1.12.0, build 8eab29e

$ docker-compose -v
docker-compose version 1.8.0, build f3628c7

Could it be that something has changed in how the compose file should be written in these newer versions of docker? Any pointers would be a huge help @5id, thanks. @5id

– JamieMason https://github.com/JamieMason/shrinkpack/pull/47#issuecomment-236623212

---

@JamieMason it looks like there was a change in the latest Sinopia Dockerfile that we were using. In docker-compose.yml, we should change image: rnbwd/sinopia to be image: rnbwd/sinopia:stable. I’m seeing another test issue arise after fixing this that I’ll look in to tomorrow.

For your own future reference, if you run docker-compose up in the package directory, it will start and show you the output for both npm & test containers (which is where I saw the NPM server exiting straight away).

– 5id https://github.com/JamieMason/shrinkpack/pull/47#issuecomment-236895153

---

[DrewML]

Awesome! I’ve got lots of packing/moving this weekend, but I’m going to try and squeeze this in during some of my rest breaks 😃

[DrewML]

I’ll give it some thought, thanks.

Cool. Happy to contribute if it’s something you want to explore further.

You can also tell Travis to spin up a separate container for each node version you’re testing against. Here is an example config from another project