Dockerfile

[verdaccio]

Dockerfile

[RnbWd]

Need to make sure it works first before publishing it anywhere

[nwhite89]

👍 I've just started to look at using sinopia, as it's so easy to set up with Docker it be great to be able to move over to this as soon as possible as sinopia is no longer being maintained.

[RnbWd]

What's nice about docker is that it automatically daemonizes sinopia as a background process, doesn't matter if it's runs locally, in the cloud, or even a raspberry pi, doesn't even require node to be installed. Once dockerized - the local fs used by sinopia becomes a portable / pluggable by default - 'detached' and flexible. The new docker beta (for local use) doesnt use virtualbox, it's tiny, fast, no env variables to be set, so its actually on par with just running it locally now. I used to only used docker in the cloud.

It's really easy, on dockerhub I linked my github repo to rebuild the docker image whenever I pushed a commit. But the development of node / docker has evolved since i first published the repo. At the time there were no other solutions, because npm enterprise didn't exist and the main company hosting private npm repos was bought by godaddy I think, so sinopia was one of the ways to for any team to share a private npm

[RnbWd]

So I don't know what combination of node / docker / distribution / modifications to sinopia would work best anymore.... We (eg anyone interested in pushing sinopia forward) need to experiment with different methods / setups because I have no idea if my repo on dockerhub still works honestly

[ambrons]

I don't think you want to use FROM node:onbuild for this container. The official stresses not using onbuild for production / long-term docker containers.

[RnbWd]

oh i wrote that as a proof of concept to see if it works. I maintained my own node / io repo for almost a year just for sinopia, because I had it running on node:slim - before the fork with joynent or jessie became stable. So one day everything broke because node:slim stopped compiling native package, so I wasn't too happy about that :P - iojs copied the same format as the official (new) node repo, so whatever image I was using disappeared. And I had to decide between two separate repos (node and io which are the same project), and running a package that minimum was 200-300mb larger than what I had been using. 😠 💢

Things are better now - fuck (excuse me) that was a crazy stressful time to be involved with node or any this. Docker's better with caching image layers, everything is more mature, etc. - there was so much bloat in these containers. Why should node - which is trivially small binary, require a 600-800mb container just to function? I dunno, I haven't read the docs for node containers in a long time. 😒

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.