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
{{ message }}
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
Hi, first thank you for taking the time to create these docker images! We're having an issue trying to run the docker image. We are getting an error requiring 'javscript run time'.. I attached a copy of the error.
Steps to reproduce
Trying to run the docker using docker compose
What is the expected correct behavior?
javascript run time should be included in the image
Relevant logs and/or screenshots
Environment
Docker/docker compose
Image version / tag: latest
Host OS: Debian -docker compose
Any logs | docker-compose.yml
Possible fixes
The text was updated successfully, but these errors were encountered:
To follow up on this, i checked the docker image and nodejs seems to be missing in the image on docker hub. Then I built the image locally and the error seems to have disappeared. So i'm guessing somehow there's a disconnect between the latest docker hub image and the dockerfile...
I'll try to launch a manual build and see if this resolves it.
I'm not really keeping this image maintained lately as I am not using it so new builds have an opportunity of breaking and may be best to use a tagged version.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
Hi, first thank you for taking the time to create these docker images! We're having an issue trying to run the docker image. We are getting an error requiring 'javscript run time'.. I attached a copy of the error.
Steps to reproduce
Trying to run the docker using docker compose
What is the expected correct behavior?
javascript run time should be included in the image
Relevant logs and/or screenshots
Environment
Docker/docker compose
Any logs | docker-compose.yml
Possible fixes
The text was updated successfully, but these errors were encountered: