search

binhex / arch-mineos-node

Docker build script for Arch Linux base with MineOS-node
GNU General Public License v3.0
2 stars 2 forks source link

Image update/rebuild to grab latest changes in mineos-node #6

Open abermudez1718 opened 1 year ago

abermudez1718 commented 1 year ago

Seems like the automated build from Apr 21 failed to build and publish. Looking at the Github Actions it seems the builds have been failing for two years. Fixing this will probably make some of the issues of people not seeing profiles go away. https://forums.unraid.net/topic/92533-support-binhex-mineos-node/page/14/

It seems hexparrot/mineos-node are using a different node version from the README.MD https://github.com/hexparrot/mineos-node/blob/master/Dockerfile#L21

In the Actions build its using node version 8 and it seems that a dep is failing.

binhex commented 1 year ago

I have posted an issue, also years ago, no response from the developer of mineos-node so not much i can do:- https://github.com/hexparrot/mineos-node/issues/471

abermudez1718 commented 1 year ago

I did some experimentation this morning according to some of the open issues and links I saw (https://github.com/hexparrot/mineos-node/issues/374. ). It seems they are using an updated version of node, specifically, 14 in their builds. (https://github.com/hexparrot/mineos-node/blob/master/Dockerfile#L21) but have not updated the main page README to reflect this.

In the arch-mineos-node image there is a default node 16 installed and the node 8 installed via nvm. I did a git reset --hard in /opt/mineos then did a git pull to get the latest from master I then did pacman -S base-devel and then a npm install using the base npm (8.1.3) from node 16. Node 8 uses npm (6.13.4). Everything seemed to build ok. I then did a chmod 777 on the local repo and started the service ./service.js using the default node version on the PATH, version 16.

dropDownFix latestGitCommit_mineos-node