sometimeskind

Webpack will always include the name of your bundled file when it's finished a build: We're keying off that file name to indicate that the watch command is ready, which...

Weirdly, it works fine under node v0.12...

Update: still occurs under iojs v2.2.1. The error appears to be caused by this line: https://github.com/tes/bosco/blob/master/src/RunWrappers/DockerUtils.js#L205

Yeah, I've got that far. It looks like there's a `checkServerIdentity` option I might be able to pass into `docker-modem`, but I'm having trouble working out why `dockerode` isn't doing...

Running `DEBUG=modem DOCKER_TLS_VERIFY= DOCKER_CERT_PATH= bosco start -wr app-employer-profile` Results in: ``` [05:57:06] Bosco: Running docker service infra-mongodb ... modem Sending: { path: '/images/json', method: 'GET', headers: {}, key: undefined, cert:...

My guess is there's a `JSON.parse` somewhere that's not handling the 'you should be using https' error that's being returned from Docker. That's just a guess though.

As suggested in that issue, running a `curl` against `/images/json` did indeed lead to all sort of certificate errors, and performing the following steps fixed them: Generate 'client' certificate: ```...

In the `package.json` for `tes-service-es6-template` we could prepend the `npm run dev` script with an `nvm use &&` which will pick up the version of node required by that service...

@tonyla's fix also worked for me. Not sure why, as the original configuration looks more correct...