Docker-node: Official docker tag deleted breaking all meteor applications

[geekgonecrazy]

• Version: 8.11.4
• Platform: official docker image

Recently we had our official image stop being able to build. The cause was the 8.11.4 tag was ~removed~ no longer supported ~from~ on the official docker repo. Surprisingly never ran into this before. We aren't certain how this is the first time for this issue.

[Edit] Bigger issue is Meteor hasn't been able to update beyond 8.11.4 which is holding back Meteor 1.8.1 and in turn keeping us stuck back on Node.js 8.11.4.

Ref:
meteor/meteor#10248
meteor/meteor#10216

[addaleax]

I’m moving this to https://github.com/nodejs/docker-node because that seems like it would be a much better place for this issue?

[tianon]

The tag wasn't deleted (it's still there), it's just no longer officially
supported (which means no more version bumps and no more base image
rebuilds for things like security updates).

[SimenB]

It's definitely still available

$ docker run -it --rm node:8.11.4 node --version
Unable to find image 'node:8.11.4' locally
8.11.4: Pulling from library/node
f189db1b88b3: Pull complete
3d06cf2f1b5e: Pull complete
687ebdda822c: Pull complete
99119ca3f34e: Pull complete
e771d6006054: Pull complete
b0cc28d0be2c: Pull complete
9bbe77ca0944: Pull complete
75f7d70e2d07: Pull complete
Digest: sha256:3422df4f7532b26b55275ad7b6dc17ec35f77192b04ce22e62e43541f3d28eb3
Status: Downloaded newer image for node:8.11.4
v8.11.4

[tianon]

As I expressed over in that Rocket.Chat thread, I think for me the
bigger concern is that apparently breaking changes were made in an 8.x
release (big enough to break Meteor, which seems pretty popular). Is
there an appropriate place that should be tracked / looked into?

[SimenB]

Probably the main repo, which @addaleax moved this from. Maybe she can move it back?

[addaleax]

@SimenB I can move it back, but without any more details there doesn’t seem to be much point in doing so? Do you know anything about the trouble that Meteor is running into?

[SimenB]

From the linked discussion

seems we'll have to wait for Meteor 1.8.1 with Node 8.15: meteor/meteor#10248
we cannot update Node version right now because there are many reports (meteor/meteor#10216) about CPU issues with Meteor 1.8.0.

I don't know anything more than that, first I've heard of it 😕

[SimenB]

Also seems really weird that Meteor haven't reported that to node directly if it's truly a regression in node itself

[nschonni]

The particular build failure on the other repo sounds a bit like this https://github.com/nodejs/docker-node/pull/846#issuecomment-413448683

[KoenLav]

I don't believe Meteor 1.8.1 is stuck waiting for something in Node.js 8.x to be fixed currently.

It was some time ago, but it seems those issues have been resolved in a later 8.x version (or an update to the fibers package).

As there have been issues which resulted in 100% CPU for a long time it's difficult to claim all of these have been resolved, but this could be the case (we're likely to find out after the 1.8.1 final(ly) is released).

So the "bigger issue" mentioned in the first post isn't really an issue, the smaller one might be?