peers/peerjs-server

Dockerfile Problem on Render.com

JAA17 opened this issue · 6 comments

JAA17 commented

I am trying to set up PeerJS Server on Render.com from a copy on my Github. (The original Github of this is here.)

Render.com sets up everything automatically in the fields when I set up a webservice.

Within the Github root directory is a dockerfile:

FROM node:alpine
RUN mkdir /peer-server
WORKDIR /peer-server
COPY bin ./bin
COPY dist ./dist
COPY package.json .
RUN npm install --production
EXPOSE 9000
ENTRYPOINT ["node", "bin/peerjs"]
CMD [ "--port", "9000", "--path", "/myapp" ]

As Render.com tries to set it up it has within its log, just before failing:

Jan 14 03:27:36 PM  Dockerfile:5
Jan 14 03:27:36 PM  --------------------
Jan 14 03:27:36 PM     3 |     WORKDIR /peer-server
Jan 14 03:27:36 PM     4 |     COPY bin ./bin
Jan 14 03:27:36 PM     5 | >>> COPY dist ./dist
Jan 14 03:27:36 PM     6 |     COPY package.json .
Jan 14 03:27:36 PM     7 |     RUN npm install --production
Jan 14 03:27:36 PM  --------------------
Jan 14 03:27:36 PM  error: failed to solve: failed to compute cache key: failed to calculate checksum of ref k0xqk3go2ko8jkmhel1pr1ugp::u02fc82vzv7zvmwdwr4k6r805: "/dist": not found

There is no dist directory in the Github Repository. Has something been modified and the Dockerfile not been updated?

jonasgloning commented

Has something been modified and the Dockerfile not been updated?

Yes :)
In the linked branch is a new Dockerfile that should work with the current repository layout. Please try it.

JAA17 commented

I watched the timestamp on the Dockerfile change in your original Github master.

Went to my Github copy to update it. But it said there were no changes.

Went back to your original Github copy and the Dockerfile has reverted to 2 years ago.

jonasgloning commented

It's published to the master branch now.

github-actions commented

🎉 This issue has been resolved in version 1.0.0-rc.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions commented

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀