dockerfile/nodejs not found

[pconerly]

I'm not sure if this is the correct place to file this, but:

When I was building a dockerfile that had FROM dockerfile/nodejs I'm getting an error: Error: image dockerfile/nodejs:latest not found

When I go to the docker registry for this repo: https://registry.hub.docker.com/u/dockerfile/nodejs/ I get redirected to https://registry.hub.docker.com/u/library/node/

Was this docker image deprecated in favor of library/node? Or was it renamed?

[sashasochka]

+1. It was OK earlier, now I get: Error: image dockerfile/nodejs:latest not found

with Dockerfile

FROM dockerfile/nodejs
MAINTAINER Oleksandr Sochka "sasha.sochka@gmail.com"

COPY . /app

# Set production settings
ENV PRODUCTION true
ENV NPM_CONFIG_PRODUCTION true

WORKDIR /app
RUN npm install
RUN npm run-script postinstall # for some reason this is not called automatically in docker

ENV PORT 80
EXPOSE 80

CMD ["node", "app.js", "--prod"]

[vmattos]

Same problem here.
Seem like the image is no longer on docker hub...

Wow, I thought the project's lemma was "Trusted Automated Docker Builds"

[sashasochka]

I switched to

FROM node:0.12

[juanpabloaj]

I have the same problem :/

[funkytaco]

👍 same here

[juanpabloaj]

I change to

 FROM node:0.10.38

and for get node 0.12

FROM node:latest

[fwachs]

I'm getting the same error but I have no way to work around it. FROM dockerfile/node:0.10.38 doesn't work either. Any solutions?

[juanpabloaj]

Federico, use this line 

FROM node:0.10.38

Without dockerfile/

—
Juanpablo AJ

On Wed, Apr 29, 2015 at 12:19 AM, Federico Wachs notifications@github.com
wrote:

I'm getting the same error but I have no way to work around it. FROM dockerfile/node:0.10.38 doesn't work either. Any solutions?

Reply to this email directly or view it on GitHub:
#11 (comment)

[sai43]

yes

FROM node:latest

its worked to me

[relwell]

This just broke for me using dockerfile/nodejs:latest

It's actually 404ing right now: https://hub.docker.com/r/dockerfile/nodejs/

[bocharsky-bw]

👍

[relwell]

This appears to have to do with the move to underscore-namespaced trusted images:

http://blog.docker.com/2015/03/updates-available-to-popular-repos-update-your-images/

I strongly encourage the old maintainers of these dockerfile-namespaced images to put in h1 text at the top of all documentation and READMEs that these have been removed in favor of new and possibly breaking images.

These repos are usually the top Google search for things like "X docker image" where X is one of the previously supported trusted images.

On Aug 18, 2015, at 11:03 PM, Bocharsky Victor notifications@github.com wrote:

―
Reply to this email directly or view it on GitHub.