node:8-slim image is broken as on 27/11/2018

node:8-slim image has been giving issues for us all day
We used an older image to verify that issues aren't from our end
Tested on multiple servers
Versions of docker in the servers:
1. Docker version 17.06.0-ce, build 02c1d87
2. Docker version 17.03.0-ce, build 3a232c8

Error in bringing up an express server:

Tue, 27 Nov 2018 10:18:13 GMT <>:server Exiting server with error { Error: read ENOTCONN
    at Socket._read (net.js:505:20)
    at Socket.Readable.read (_stream_readable.js:442:10)
    at resume_ (_stream_readable.js:822:12)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickDomainCallback (internal/process/next_tick.js:219:9)
    at Function.Module.runMain (module.js:696:11)
    at startup (bootstrap_node.js:204:16)
    at bootstrap_node.js:625:3 errno: 'ENOTCONN', code: 'ENOTCONN', syscall: 'read' }
Tue, 27 Nov 2018 10:18:13 GMT <>:server Clean error exit. Pool drained
Tue, 27 Nov 2018 10:18:13 GMT <>:server Exiting server with error 1

node:6-slim is still Debian 8 jessie based as of ed3e8825 master
node:8-slim is Debian 9 stretch based since 0ceefee master
node:10-slim is still Debian 8 jessie based as of ed3e8825 master
node:11-slim seems to be Debian 9 stretch based since daf910e master

Pretty confusing. node:8-slim was changed by accident?

Jessie is EOL so we are transitioning to stretch. Pr #850 will give you the option to target either one for slim.

@LaurentGoderre

@LaurentGoderre is there any way to subscribe to these update notices via some rss feed or newsletter? For example, we're generally aware of nodejs security releases because of their google group: https://groups.google.com/forum/#!forum/nodejs-sec . Is there anything similar in nature for docker-node ?

Not sure we have such communication channel set up yet.

@shrikrishnaholla

@shrikrishnaholla you docker-library/official-images#5125 will introduce the node:8-jessie-slim which will probably help fix your issue.

@LaurentGoderre

@LaurentGoderre may I know when this is expected to be pushed to docker hub? I'm still getting the error that the tag isn't found

When docker-library/official-images#5126 is merged, it'll be available a couple of hours later

all of sudden, the git binary is also missing in node:8-slim 😕

@macrozone

@macrozone git has never been installed in the slim variants.

@chorrel i just noticed, because yarn install suddenly failed. But it was because i used a git url as dependency in package.json.

Just heads up for others: dont use the slim image if you need npm or yarn install

@marco you _can_ use slim images to install regular packages from npm. If you want to install from git, you'll need to extend the image and install git yourself. Then those npm/yarn installs will work

…

On Tue, Dec 4, 2018 at 4:52 PM Marco Wettstein ***@***.***> wrote: @chorrel i just noticed, because yarn install suddenly failed. But it was because i used a git url as dependency in package.json. Just heads up for others: dont use the slim image if you need npm or yarn install — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#936 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABHEehSBm0SB98jHo7sh_nwD5RzaxtOeks5u1lrggaJpZM4Y1rUv> .

-- Shrikrishna Holla Author, Programmer, Human Github <https://github.com/shrikrishnaholla/> | LinkedIn <http://www.linkedin.com/in/shrikrishnaholla> | Twitter <https://twitter.com/srikrishnaholla> | Facebook <https://www.facebook.com/shrikrishna.holla> | srikrishna_holla on Skype | shrikrishna on freenode irc

You can also use the slim image with multi-stage build to address this issue like you would in Alpine

I believe we can close because we not have jessie-slim and stretch-slim tags

Navigation Menu

Repository navigation

node:8-slim image is broken as on 27/11/2018 #936

Error in bringing up an express server:

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

node:8-slim image is broken as on 27/11/2018 #936

Description

Error in bringing up an express server:

Activity

tvainika commented on Nov 28, 2018

LaurentGoderre commented on Nov 28, 2018

shrikrishnaholla commented on Nov 28, 2018

LaurentGoderre commented on Nov 28, 2018

LaurentGoderre commented on Nov 29, 2018

shrikrishnaholla commented on Dec 2, 2018

SimenB commented on Dec 2, 2018

macrozone commented on Dec 3, 2018

chorrell commented on Dec 4, 2018

macrozone commented on Dec 4, 2018

shrikrishnaholla commented on Dec 4, 2018

LaurentGoderre commented on Dec 4, 2018

LaurentGoderre commented on Dec 4, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions