Skip to content
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

Docker image fails with "Error: Cannot find module '/usr/src/app/build/server.js" #256

Closed
ed-holland opened this issue Oct 4, 2020 · 11 comments · Fixed by #257
Closed

Comments

@ed-holland
Copy link

The current docker image produces messages like the below:

image

Is this the same issue as #253?

@sbcgua
Copy link
Collaborator

sbcgua commented Oct 4, 2020

yes, I'm working on it.

@ed-holland
Copy link
Author

The current docker image still has the problem. Can you force publishing it?

@larshp
Copy link
Member

larshp commented Oct 5, 2020

it did publish a new version

@larshp larshp reopened this Oct 5, 2020
@sbcgua
Copy link
Collaborator

sbcgua commented Oct 5, 2020

are you sure you're using the latest image ? Just tried this:
image

@ed-holland
Copy link
Author

Just pulled the new version, but still the same issue.
image

image

@sbcgua
Copy link
Collaborator

sbcgua commented Oct 5, 2020

I'm very certain there is some issue with the pulling. I can see the digest in your screenshot differs from the last images at dockerhub.
image

Do have an access to command line ? COuld you try pulling it with a specific tag ?

image

@ed-holland
Copy link
Author

yes, Portainer allows that. This issue has not changed. Still there.

image

The image is now showing with two tags (must have been this version already)
image

@sbcgua
Copy link
Collaborator

sbcgua commented Oct 5, 2020

ok ... ehm ... but I cannot reproduce the issue really. Do you have an access to command line ? Could you docker ps -a and docker image ls there (pls mind other private containers if you have ones :)

@ed-holland
Copy link
Author

Hope this helps
image

@sbcgua
Copy link
Collaborator

sbcgua commented Oct 5, 2020

hmm, looks OK ...
so ... what happens if you run:

docker ps -a | awk '{ print $1,$2 }' | grep abaplint | awk '{print $1 }' | xargs -I {} docker rm {}
docker run --rm -p 3000:3000 abaplint/abaplint-backend

The first command removes all abaplint containers (just in case)

@ed-holland
Copy link
Author

Interestingly enough, just deleting and recreating the container using my compose file resolved the issue.
Very strange. Thanks a lot for helping me getting through this.

Details are now also showing up (using verbose)
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants