Pm2: gpgkey : CDN limit exceeded

[gulien]

Hello 👋

In my Dockerfile (debian stretch), I use the following command to install PM2:

$ curl -sL https://raw.githubusercontent.com/Unitech/pm2/master/packager/setup.deb.sh | bash -

It does not work anymore and after some investigation it seems that the root cause is because the URL https://packagecloud.io/Keymetrics/pm2/gpgkey is broken (Bandwidth or Storage Limit Exceeded).

This URL is used here in the install script: https://github.com/Unitech/pm2/blob/master/packager/setup.deb.sh#L155

Thank you 😄

(related: https://github.com/thecodingmachine/gotenberg/issues/35)

[vmarchaud]

It seems that we have an issue with our repository provider (packagecloud.io), i will try to reach them

[gulien]

Hello @vmarchaud! Any news about this issue 🙂?

[karakanb]

This still seems to be an issue, are there any updates around this? Maybe a potential workaround?

[Sten-H]

Also curious about this. I edited build/base/Dockerfile to install pm2 with npm, which worked, but when running gotenberg pm2 fails to launch chrome headless and just keeps retrying. It didn't really log why it couldn't start it, just that it was retrying.

[gulien]

@Sten-H I tried it too and indeed Chrome did not behave as expected (but pm2 is able to launch it). I’m wondering if the pm2 install script adds something else in the system.

[karakanb]

I think it adds an additional repository which is not a valid debian repository, I don't get the same error but I get 429 Too Many Requests when I run apt-get update, which tries to reach to that repository but cannot find a release file. The repository seems to be coming from packagecloud.io, which seems to be throttling package installs, that is why I think these two issues are related. Right now I am unable to install anything on a base image that has PM2.

[vmarchaud]

Here's some explanation :
We used packagecloud.io for publishing our image of pm2 before, we paid initially 20$/m which was reasonable for us. They increased the pricing two month afterwards to 75$/m (>200% increase), which was too important for us.
Since they offer a open source plan, i requested them (at the time of my first answer to this issue) to opt into this plan. They sadly didn't answered.
I'm sorry but i believe you will need use the npm/yarn installation method from now on.
If you have any issue, it's because the apt repo has a custom installation (see our script)

[gulien]

Thank you @vmarchaud. I'll try to mimic this custom installation and see if it works as previously.

[gulien]

Ok so in order to make my program to work as expected with PM2, I've simply copied all the PM2 related file from my previous image:

FROM thecodingmachine/gotenberg:3.2.0 AS hack
FROM debian:9.5-slim

RUN curl -sL https://deb.nodesource.com/setup_9.x | bash - &&\
    apt-get install -y nodejs

COPY --from=hack /usr/bin/pm2 /usr/bin/pm2
COPY --from=hack /usr/share/pm2 /usr/share/pm2
COPY --from=hack /etc/default/pm2 /etc/default/pm2
COPY --from=hack /etc/systemd/system/pm2.service /etc/systemd/system/pm2.service