-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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: slim docker image to 154Mb #5248
Conversation
@barakbd can you tell me if this version of the dockerfile work for you? |
Codecov Report
@@ Coverage Diff @@
## master #5248 +/- ##
==========================================
- Coverage 93.88% 93.86% -0.03%
==========================================
Files 123 123
Lines 8965 8965
==========================================
- Hits 8417 8415 -2
- Misses 548 550 +2
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. easy to read and understand.
@flovilmart - will check soon. |
The tests are running against node 10. We’ll update the CI setup to effectively run always against lts |
There is an issue with the image built using your Dockerfile, not sure what it is.
But when I call that API using image parseplatform/parse-server:3.0.0 or the image built with my Dockerfile, I get:
|
How did you mount / run it? |
|
@barakbd I just ran a simple test: from this branch run:
the run the server:
Note the database is clean and was just created before the 1st start Then run:
And I have the following result:
|
If it works for you then go ahead and merge to master, and build a new image for Dockerhub. |
@barakbd that's not the point, I am trying to avoid a regression if there is any. Did you try in another context like directly using the docker image? |
@barakbd I also realized the
https://docs.docker.com/engine/reference/builder/#volume Perhaps this was your issue |
d64613e
to
800a8be
Compare
I tested again, still not working when running with a local mongodb docker. |
Well, that doesn’t help much. What do you mean by ‘not working’? Is the Schema still the same? Are there any logs? Is the master branch showing a proper behaviour? |
Have you tried running it with the docker compose setup in the repo I sent? |
I still get
|
I simply ran What are the logs from the container when started with —verbose=1 |
@barakbd I attempted to run your docker compose project and you can find the logs there: https://gist.github.com/flovilmart/dfc72624d44201c6c37dabc1f640a7e9 This doesn't look good, as the DB gets killed and then restarted, at the time the server starts, the DB is not up. This doesn't look related to those changes. |
If you look closely to the logs, we see:
And on a following restart:
So there seems to be an issue with your docker compose setup:
|
It looks like you are running master. checkout dev branch and then run docker-compose up. |
Why don’t you try with the built image? Can you provide the logs when starting please? |
Which built image? |
The image built from the repository. And no I haven’t tested the dev branch, have you? Can you provide the logs when starting up? |
@barakbd I tested with your dev branch, and it is still failing when running
However, if you |
@flovilmart @acinader @barakbd @barakbd-bluevine Seems this PR wasn't properly tested. I currently got this error (#5778) and discovered, after rollback the base image from Let me know how should I go with. By the way, the official document of package |
* Better dockerfile * nits * proper VOLUMES
No description provided.