search

metacpan / metacpan-docker

DEVELOPMENT Docker configs for MetaCPAN
Artistic License 2.0
26 stars 23 forks source link

Service 'web' failed to build #67

Closed srchulo closed 4 years ago

srchulo commented 4 years ago

I am running these steps from the README:

git clone https://github.com/metacpan/metacpan-docker.git
cd metacpan-docker
bin/metacpan-docker init

And then I run:

bin/metacpan-docker localapi up

However, the command fails and I get this output:

E: Version '10.17.0-1nodesource1' for 'nodejs' was not found
ERROR: Service 'web' failed to build: The command '/bin/bash -o pipefail -c curl -sL https://deb.nodesource.com/setup_10.x | bash     && curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -     && echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list     && apt-get update     && apt-get install -y -f --no-install-recommends nodejs=10.17.0-1nodesource1 yarn=1.19.2-1     && apt-get clean     && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
oalders commented 4 years ago

@ssoriche any idea why localapi fails to start because of a metacpan-web error?

oalders commented 4 years ago

@srchulo if you're motivated to fix the web end of things, you could take a look at https://github.com/metacpan/metacpan-web/blob/master/Dockerfile

I think the choice of node version is somewhat arbitrary.

srchulo commented 4 years ago

@oalders replacing nodejs=10.17.0-1nodesource1 with nodejs allowed the image to be built past that step. The version of nodejs that it did install for me was 10.18.1-1nodesource1, in case it should be pinned to something.

I did then run into issues installing the CPAN modules, but that's probably a separate issue:

fork: Cannot allocate memory at /usr/local/lib/perl5/site_perl/5.30.1/Command/Runner.pm line 174.
FAIL install HTML-Tree-5.07
# more fails
oalders commented 4 years ago

@srchulo thanks. If you want to send a PR for the nodejs changes, we can get that merged.

For the CPAN modules, what's the installer being used? If it's cpm you could try setting --workers to a lower number (it defaults to 5) to see if that helps with memory allocation.

srchulo commented 4 years ago

@oalders pull request created.

And yeah, it was using cpm. This time it seemed do install fine, so I don't know what the issue was before.