-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node.js issue when deploying with Docker #831
Comments
Hi @wkulesza, Cheers! |
Thanks for reporting this! We've experimented with dockerizing datatools-ui (and the server) in the past, and it's definitely something we're interested in doing. We ran into similar issues when we were setting it up. It seems to be an issue with mastarm. The solution we came up with was the following: # syntax=docker/dockerfile:1
FROM node:14
WORKDIR /datatools-build
RUN cd /datatools-build
COPY package.json yarn.lock /datatools-build/
RUN yarn
COPY . /datatools-build/
COPY configurations/default /datatools-config/
RUN yarn run build --minify -c /datatools-config
FROM nginx
COPY --from=0 /datatools-build/dist /usr/share/nginx/html/dist/
EXPOSE 80 Please keep in mind that this is very experimental and will probably not work out of the box, however I hope it may help you get on the right path towards getting things working! If you do get it working, please do report back here and we might be able to upstream some of your work. |
Hi @miles-grant-ibigroup , |
Hi @miles-grant-ibigroup ,
and afterwords the entire folder content
to the same target folder? On the first glance, it looks like the first copy operation is redundant. What is your opinion on this? |
We found that some of the other files in the directory sometimes interfere with the yarn install. As I said this docker file was quite experimental and a "production" version probably wouldn't need this better-safe-than-sorry extra copy. Hope that's helpful! |
@dancesWithCycles @miles-grant-ibigroup hi, we successfully managed to get DT running in docker using this setup: https://github.com/javandres/gtfs_editor_ibi_datatools_docker |
Glad you were able to get it working @wkulesza! Good news about auth0 we are currently in the process of upgrading the version of the auth0 library we use and that should resolve some of the issues you're having! |
Hi @wkulesza , |
Sure:
|
Hi folks, @wkulesza: May I ask you what operating system version you are using as host? Do you mind sharing something like this.
|
@wkulesza Do you mind sharing something like this.
|
@wkulesza Do you mind sharing something like this.
|
Is is a little bit daunting. No matter what I did so far, the datatools-ui container keeps failing after seconds like this.
My motivation is gone now. I am going for a motivation hunt next week to figure out how to proceed. Thanks everyone for all the help already. Cheers! |
@dancesWithCycles - sure, but i dont think it matters, as everything happens in the docker.
Let me know how you get on ? Good idea is to go to /var/lib/docker/containers/ - there you should see each container and inside, you have a log file that would show you what's wrong. if a docker container is stopped, make sure to see which id it has using docker ps -a |
Hi folks,
Thank you so much for providing and maintaining this repository! Kudos!
Observed behavior
With all configurations I tried so far the Docker container for datatools-ui is terminating after seconds with the following reply.
Expected behavior
I expected the datatools-ui container to run in an orchestra together with the other four container for datatools-server, postgres, nginx and mongodb.
Steps to reproduce the problem
I am using the following repository to configure the Docker composition.
https://github.com/javandres/gtfs_editor_ibi_datatools_docker
Any special notes on configuration used
I adjusted the Dockerfile of the repository for datatools-ui and tried the following settings one after another.
No matter what settings, I am ending up with the same failure killing the datatools-ui container after a couple of seconds.
I am appreciating any hint that helps me tackle this issue.
Cheers!
The text was updated successfully, but these errors were encountered: