Change dockerfile to use local version as opposed to cloning polkadot…

[philipstanislaus]

…-js/apps

The current behavior does not allow the dockerfile to be used with forked repositories.

[philipstanislaus]

For some reason, the copy step in the second stage of the docker build fails. Any idea why that might be?

Step 13/15 : COPY --from=builder /app/apps/packages/apps/build /var/www/html
COPY failed: stat /var/lib/docker/overlay2/78169e8f13a4f8ee86c8ff2957570b635166288e8a92983c8516f80d67986fe2/merged/app/apps/packages/apps/build: no such file or directory

[jacogr]

@philipstanislaus No idea what causes it, honestly have not played with this for quite some time now. Will take a look though, it should be something small

[jacogr]

Ok, so believe it is this line - COPY --from=builder /app/apps/packages/apps/build /var/www/html

When cloning, it clones it into the apps directory, so adjusting the above to the following should work (I believe) - COPY --from=builder /app/packages/apps/build /var/www/html (Replacing /app/apps with /app)

(And probably updating the workdir as well, checking now...)

Update, yes, this does the trick for me on your branch -

FROM ubuntu:18.04 as builder

# Install any needed packages
RUN apt-get update && apt-get install -y curl git gnupg

# install nodejs
RUN curl -sL https://deb.nodesource.com/setup_10.x | bash -
RUN apt-get install -y nodejs

WORKDIR /apps
COPY . .

RUN npm install yarn -g
RUN yarn
RUN NODE_ENV=production yarn build

FROM ubuntu:18.04

RUN apt-get update && apt-get -y install nginx

COPY --from=builder /apps/packages/apps/build /var/www/html

EXPOSE 80

CMD ["nginx", "-g", "daemon off;"]

(We are building way too much here though, it should only do the webpack thing, but not your issue - I'll update when this PR goes in)

[jacogr]

Thanks a million! (I just applied my small updates to the branch)

[philipstanislaus]

Awesome, thanks @jacogr for the fast turnaround. Just tested this locally, works like a charm.

[polkadot-js-bot]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.