Node Docker image broken

#1

Post by lingz » Fri, Mar 16, 2018, 11:29 AM UTC

Re: Node Docker image broken

#2

Post by dozzie » Fri, Mar 16, 2018, 12:31 PM UTC

Ah yes, this happens from time to time when you use somebody else's repositories with somebody else's package retention. That's why production should only use repositories that change in ways that are predictable to you (OS upstream, your own, and usually nothing else).

Re: Node Docker image broken

#3

Post by blablabla123 » Fri, Mar 16, 2018, 3:23 PM UTC

dozzie wrote: post #2

Ah yes, this happens from time to time when you use somebody else's repositories with somebody else's package retention. That's why production should only use repositories that change in ways that are predictable to you (OS upstream, your own, and usually nothing else).

Amen.

Re: Node Docker image broken

#4

Post by zackify » Fri, Mar 16, 2018, 3:34 PM UTC

This is one of the reasons I never use the latest version of any docker image, so I don’t repeat my constant struggles with npm packages breaking on minor version changes

Edit:

I see they were overwriting current tags.... well that’s even worse

Re: Node Docker image broken

#5

Post by Cthulhu_ » Fri, Mar 16, 2018, 3:38 PM UTC

zackify wrote: post #4

This is one of the reasons I never use the latest version of any docker image, so I don’t repeat my constant struggles with npm packages breaking on minor version changes Edit: I see they were overwriting current tags.... well that’s even worse

Latest should only be used for hackery / development, but please fix it to a stable version before release.

Overwriting tags should honestly not be possible, ever. Node / NPM did that (I think) with one of their versions too. Or was it a npm package?

Re: Node Docker image broken

#6

Post by tkone » Fri, Mar 16, 2018, 3:55 PM UTC

well i mean it's broken if you use yarn. which isn't a standard part of node, so like, not really?

Re: Node Docker image broken

#7

Post by bearjaws » Fri, Mar 16, 2018, 3:57 PM UTC

Never ever use :latest unless its in your docker-compose DEV file. Try to treat docker images like you would dependencies.

We always lock down to specific versions, but we also use a self hosted docker mirror to cache everything anyway.

Re: Node Docker image broken

#8

Post by moondev » Fri, Mar 16, 2018, 4:06 PM UTC

bearjaws wrote: post #7

Never ever use :latest unless its in your docker-compose DEV file. Try to treat docker images like you would dependencies. We always lock down to specific versions, but we also use a self hosted docker mirror to cache everything anyway.

other labels are mutable too though. That's why this broke for other tags beside latest. Use the hash instead for a hard link, but obviously won't get any security updates.

Re: Node Docker image broken

#9

Post by moondev » Fri, Mar 16, 2018, 4:07 PM UTC

Cthulhu_ wrote: post #5

zackify wrote: post #4

This is one of the reasons I never use the latest version of any docker image, so I don’t repeat my constant struggles with npm packages breaking on minor version changes Edit: I see they were overwriting current tags.... well that’s even worse

Latest should only be used for hackery / development, but please fix it to a stable version before release. Overwriting tags should honestly not be possible, ever. Node / NPM did that (I think) with one of their versions too. Or was it a npm package?

Use the hash instead of the label. Labels being mutable is helpful because you if you want the most current, bugfixed version of node 7.. node:7

Re: Node Docker image broken

#10

Post by timwis » Fri, Mar 16, 2018, 4:38 PM UTC

dozzie wrote: post #2

Ah yes, this happens from time to time when you use somebody else's repositories with somebody else's package retention. That's why production should only use repositories that change in ways that are predictable to you (OS upstream, your own, and usually nothing else).

huh? so like, don't use open source libraries?