You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see that the command is creating the docusaurus folder and when I create a "test" folder in it and restart the container it creates a node_modules folder and yarn.lock file. So permission issues shouldn't be the case.
Still, the log output is:
Variables:
- UID=99
- GID=100
- AUTO_UPDATE=true
- WEBSITE_NAME=test
- TEMPLATE=classic
- RUN_MODE=development
/* Register a new cron job for auto updating... */
/* Successfully registered. */
/* Docusaurus configuration already exists in the target directory /docusaurus */
/* Node modules already exist in /docusaurus/test/node_modules */
/* Start supervisord to start Docusaurus... */
2023-03-14 09:40:04,107 INFO Set uid to user 0 succeeded
2023-03-14 09:40:04,108 INFO supervisord started with pid 11
2023-03-14 09:40:05,111 INFO spawned: 'docusaurus' with pid 12
/* Will run this Node service as development mode... */
yarn run v1.22.19
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2023-03-14 09:40:05,276 INFO exited: docusaurus (exit status 1; not expected)
2023-03-14 09:40:06,278 INFO gave up: docusaurus entered FATAL state, too many start retries too quickly
The text was updated successfully, but these errors were encountered:
I got the same issue as stated in#5 but couldn't resolve it.
I try to create the container under Unraid so the command looks a bit different than usual but for general useability it should be the same.
I can see that the command is creating the docusaurus folder and when I create a "test" folder in it and restart the container it creates a node_modules folder and yarn.lock file. So permission issues shouldn't be the case.
Still, the log output is:
The text was updated successfully, but these errors were encountered: