docker freaks out if you use -h:

2013/12/02 20:29:41 Error: create: ExportEnv json: cannot unmarshal number into Go value of type string

I've tried -e HOSTNAME=ip but no dice, maybe we should use a different env var? I tried changing that myself but it seems to confuse kappa, digging into kappa now

searching for where kappa logs but I'm assuming by default it's just stdout or something so we're missing that

During NPM install, ./load-views.sh has been run and unexpected EOF is thrown.
I don't understand anything about what causes this, so I post it here.

To fully understand, here all the logs: https://gist.github.com/LoicMahieu/f33386eef799914e4348

Thanks.

I have a registry we've been running for a few months now (pre-kappa) and I'd like to update the image.

I was wondering if there are any recommendations on how I should go about this.

We probably shouldn't be shipping npmjs in Admin Party mode.

HOSTNAME can't contain periods, so we should use $HOST as the vhost.

Would people prefer that this live in two containers? For example, one for npmjs and one for npm-delegate? Or do people like the integrated approach I went with originally here?

Right now the Dockerfile delegates entirely to the setup scripts, allowing for none of the container to be cached. Refactor this code to allow better caching support

Heh

Networking is a bit of a hack right now, external ports have to exactly match internal ports for the system to work properly, due to how npm-delegate checks the npmjs instance and how it refers the client to downloading the package.

Allowing these ports to be more flexible would be nice. The best solution requires an upstream fix, but I think we can still be more flexible with our startup flags.

There's no indication within this repository of any sort of version number or Docker support range. The node community has this whole notion of “semver” I've completely through out the window!

Within this community, the version number seems to generally be in the header block of the Dockerfile, though we should probably also include it in the README.

oddly this didn't happen in my vm but I'm chucking npm up on ec2 and now it's barfing:

2013-12-01T19:53:38.712Z INFO,REQUEST 96.50.97.111 PUT /-/user/org.couchdb.user:tjholowaychuk 404
[Sun, 01 Dec 2013 19:54:18 GMT] [error] [<0.264.0>] Could not open file /usr/local/var/lib/couchdb/registry.couch: no such file or directory
[Sun, 01 Dec 2013 19:54:18 GMT] [info] [<0.219.0>] 172.17.0.22 - - PUT /registry/_design/app/_rewrite/-/user/org.couchdb.user:tjholowaychuk 404

can't seem to get anything installing, I'll look into it but there might be something we should add to the docs, or if you know what this is that works too :D

or my setup: docker -d with http_proxy (docker hello world example runs fine)

pschu@senatov:~> docker build --quiet=false -t  npmjs github.com/terinjokes/docker-npmjs
2014/04/01 22:17:39 Error: )
pschu@senatov:~> docker --version
Docker version 0.9.1, build 867b2a9

The CouchApp database that backs npmjs should exist outside the container, to allow for easy upgrades of the container without losing the entire database.

Kappa should be bound to the external interface only, and couchdb to the internal interface on the same port. Tarball GETs can flow through Kappa just fine, and we think it would simplifies the port exports.

still get this at seemingly random times, it was working fine for a few hours and then destroyed itself somehow haha

Just checking, does this line contain the correct URL https://github.com/terinjokes/docker-npmjs/blob/master/scripts/setup.sh#L39 ?

docker freaks out since it's not a real hostname, but I think this more of a kappa issue, just opening here too in case someone else runs into this krakenjs/kappa#11

I keep getting ECONNREFUSED.

the /root/startup.shscript complains about about /etc/hosts being on a Read-only filesystem (and hapi not existing):

root@37ca54227a47:/# /root/startup.sh: line 3: /etc/hosts: Read-only file system
Apache CouchDB has started, time to relax.
                          {mochiweb_request_qs,[{"new_edits","false"}]},
/root/startup.sh: line 5: hapi: command not found
                          {couch_rewrite_count,0},
                          {mochiweb_request_recv,true},
                          {mochiweb_request_cookie,[]}]},
                        {trap_exit,false},
                        {status,running},
                        {heap_size,10946},
                        {stack_size,24},
                        {reductions,10675}],
                       []]}}

CouchDB is accessible however.