Laurent Goderre

That run command would not be useful if you override it with a volume mount in you compose though no?

I don't think it's practical to pin the version because the OS and Node version don't line up. There is an inherent risk to using shortcut tags and it's a...

@kzantow done!

Running it on the Kong image here is what we get!! https://hub.docker.com/_/kong ``` NAME VERSION TYPE LPeg 1.0.2-1 lua-rocks LuaFileSystem 1.8.0-1 lua-rocks ansicolors 1.0.2-3 lua-rocks binaryheap 0.4-1 lua-rocks etlua 1.3.0-1...

@pombredanne fyi

@kzantow Updated

@kzantow updated

Depending how you orchestrate your containers, an init container could do the trick. No need for a seperate image.

Minimally reproducible with: ``` docker run --rm -it node:18-alpine sh ``` ``` apk add --no-cache --virtual .gyp python3 make g++ > /dev/null npm install -g re2 > /dev/null ``` ```...

This fix upstream could help: https://github.com/gperftools/gperftools/issues/693#issuecomment-173898629