"Run Sassy yourself with Docker" instructions out of date?

Hi, I know this is "experimental" but I've been trying to follow the Run Sassy yourself with Docker instructions but I seem to be running into an error connecting to a local Redis database.

Do I need to do something differently to get Sassy running with Docker?

ac-koa-hipchat-sassy$ sudo docker logs sassy
{ Error: Cannot find module '../build/Release/bson'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/src/node_modules/bson/ext/index.js:15:10)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at require (internal/module.js:20:19) code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version
info: Atlassian Connect add-on started at http://192.168.1.232:3020
events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
    at RedisClient.on_error (/src/node_modules/redis/index.js:196:24)
    at Socket.<anonymous> (/src/node_modules/redis/index.js:106:14)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at emitErrorNT (net.js:1284:8)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Comments (2)