facing a problem while running Sandstorm inside a Docker container

[manjui...@gmail.com]

Hi

While I could successfully build and run Sandstorm's docker image from the Dockerfile (available in Github), for some reason, I am not able to connect to the sever running inside the container.

'wget' says:

Connecting to local.sandstorm.io (local.sandstorm.io)|127.0.0.1|:6080... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.

Any thoughts where I am I going wrong?

Thanks!
Manjunath D

[manjui...@gmail.com]

Some more details:

--- I have sandstorm installed on the host too. However, I make sure I stop it (killall -9 *sandstorm*) before creating the docker container.

--- 'netstat' inside the container shows only the Mongo port 6081 and 6080 is missing!

--- 'ps -A' inside the container indeed shows 'sandstorm' processes.

Thanks!
Manjunath D

[Kenton Varda]

Jason (cc'd) can probably answer this best since he wrote the Dockerfile.

Note that we primarily wrote it for use in our CI build. I'm not sure if anyone has tried using it for actual deployment, though we would like it to work for that purpose as well.

-Kenton

--
You received this message because you are subscribed to the Google Groups "Sandstorm Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sandstorm-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jason Paryani]

How are you starting the docker container? Make sure to use '-p' to map the port back to the host (usually I do something like `docker run -p 6080:6080 -t sandstorm -d`).

If that's not the problem, then can you send me the contents of $HOME/sandstorm/var/log/sandstorm.log? It should contain some error message pointing to the problem.

[manjui...@gmail.com]

Hi Kenton and Jason,

Thanks for the response.

I am mapping the port 6080. The error that I found in sandstrom.log is:


/programs/server/node_modules/fibers/future.js:173
throw(ex);
^
Error: Cannot find module 'es6-promise'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.Npm.require (/programs/server/boot.js:95:18)
at Package (packages/capnp/import.js:1)
at /programs/server/packages/capnp.js:19:4
at /programs/server/packages/capnp.js:26:3
at /programs/server/boot.js:168:10
at Array.forEach (native)
** Front-end died immediately after starting.
** Sleeping for a bit before trying again...

[Jason Paryani]

That's very strange. Can you try doing `make clean .docker` again, and see if you get the same error?

Also try out `docker run -p 6080:6080 -d -t jparyani/sandstorm` to see if you can run sandstorm using my image from the docker hub repository.

[manjui...@gmail.com]

Thanks, Jason.

While your image works perfectly, rebuild (make clean .docker) threw the following error this time:

"Errors prevented bundling:
While building package `capnp`:
error: couldn't install npm packages from npm-shrinkwrap"

I reinstalled meteor, but no luck.


Other installation details that may be useful:

1)
For installing Cap'nProto, I used instructions under "Building from Git with Autotools", so that release version is NOT installed.

2)
sudo npm install jsontool
npm WARN deprecated json...@7.0.2: jsontool is now called simply 'json'. Please update your dependencies.
json...@7.0.2 node_modules/jsontool

3) because of the above warning, I also installed:
sudo npm install json

Manjunath

[Jason Paryani]

Sorry this a temporary build problem with Sandstorm (see https://github.com/sandstorm-io/sandstorm/issues/145). You can revert Cap'n Proto and Sandstorm to commits from about a week ago and try again, or wait for that issue to get fixed.

[manjui...@gmail.com]

Both build and Sandstorm inside a Docker container work very fine with older versions of Cap'nProto and Sandstorm (committed 2 weeks back).

Thanks a lot!