lichocker run image errors

[Bugouser]

Hi, i am having issue running lichocker

This is console output:

[root@localhost lichocker]# docker run \
>     --volume /opt/lichocker/lila:/home/lichess/projects/lila \
>     --volume /opt/lichocker/lila-ws:/home/lichess/projects/lila-ws \
>     --publish 9663:9663 \
>     --publish 9664:9664 \
>     --name lichess \
>     --interactive \
>     --tty \
>     brandone211/lichess
27:C 15 Jan 15:56:18.061 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
27:C 15 Jan 15:56:18.066 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=27, just started
27:C 15 Jan 15:56:18.066 # Configuration loaded
nohup: appending output to '/home/lichess/nohup.out'
about to fork child process, waiting until server is ready for connections.
forked process: 71
child process started successfully, parent exiting
building ui modules with target=dev and mode=build
node: v13.5.0
yarn: 1.21.1
ls: cannot access 'node_modules': No such file or directory
ls: cannot access 'node_modules/@*': No such file or directory
ls: cannot access 'ui/node_modules': No such file or directory
ls: cannot access 'ui/*/node_modules': No such file or directory
mkdir: cannot create directory 'public/compiled': Permission denied
cp: cannot create regular file '.sbtopts': Permission denied

Lichocker installed to /opt/lichocker. Directory contains folowing files and subdirectories: ├── build ├── Dockerfile ├── lila ├── lila-ws ├── README.md └── run.sh

[Bugouser]

Adjusting permissions solved the issue. I did chmod 777 -R "my local lila and lila-ws path".

[ankitshubham97]

Writing here just in case someone stumbles upon the same problem I was having. I was trying to install lila directly on a host (no docker) and I had all the dependencies met. But I was getting following error and build wouldn't proceed:

~/lila$ ./ui/build 
building ui modules with target=dev and mode=build
node: v10.19.0
yarn: 0.32+git
ls: cannot access 'ui/*/node_modules': No such file or directory
Usage: yarn [options]

yarn: error: no such option: --non-interactive

Turned out I had used apt-get to install yarn but it apparently installed cmdtest! This was the command:

~/lila$ sudo apt-get install yarn
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'cmdtest' instead of 'yarn'
cmdtest is already the newest version (0.32.14.gcdfe14e-1).

The solution was to remove cmdtest (I did not need it; it was a fresh host dedicated to lila) and run the following commands:

sudo apt remove cmdtest
sudo apt remove yarn
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn

Reference: https://github.com/Joystream/helpdesk/issues/16