Exceptions in make initdb
#1511
Comments
|
@Carreau Can you include everything after the |
|
This might be because we recently upgraded to ElasticSearch 5.0 in #1494. Docker doesn't seem to rebuild containers when the |
|
Thanks @di , No it does not works, and as a output is ... a bit long I pasted it in a gist. I also try to nike all container and images |
|
@Carreau Hmm. After running |
|
Hum you are right it is not running and I have these line in the middle of my logs: it does not affect me for what I am trying to accomplish right now. I'll try to keep an eye to see if I can figure out what make it fail. |
|
Since those logs are all mixed between containers, the output of just |
|
Ha yes, that's immediately more obvious: |
|
Ok, After stopping Docker-machine and pushing the Max RAM in VirtualBox.app to 4Gb I get the following: So now I probably need to figure out how to increase the max virtual_memory. It seem to be a know problem though I'm unsure how to fix it on my side. |
|
@Carreau If you haven't seen it already, the thread at docker-library/elasticsearch#98 might help you. A better alternative, if possible, might be switching from using VirtualBox as the host OS to using "Docker for Mac" instead: https://docs.docker.com/engine/installation/mac/ I'm going to close this issue for now because this isn't a problem with Warehouse per se, but please feel free to keep it updated if you have additional difficulties, or reopen if we need to update some documentation, etc! |
|
Thanks, yes I saw that issue, havent figured out exactly how to fix it on my system but its not preventing me to work for now. So no issue. Thanks. |
|
Even I stumbled upon this. From https://www.elastic.co/guide/en/elasticsearch/guide/current/_file_descriptors_and_mmap.html:
@di maybe this can be added to the Getting Started page in the Warehouse docs? |
|
Ignore that. I spoke prematurely. |
|
Okay. So, |
|
@pradyunsg Yes, this has been a recurring issue. I've created #2811 to document the memory requirements. |
The current settings for the elasticsearch container place the started node in "production, single node cluster" mode. This performs boostrap tests, one of which tests for virtual memory via the `sysctl` setting of `vm.max_map_count`. In certain Docker-in-Docker development environments, the end user may not have access to the underlying host settings, and cannot modify this setting. An alternative is to set the `discovery-type` to a single node, placing the service in "development mode", turning any bootstrap checks from errors to warnings. Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/system-config.html#dev-vs-prod Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/bootstrap-checks.html Originally reported in #1511, related to pypi#4370 Signed-off-by: Mike Fiedler <miketheman@gmail.com>
* chore(dev): set web to depend on db When running `make tests`, the current expectation is that the user has executed `make serve` and the database container is running in already. This brings in all the other runtime dependencies, when all the tests need is a running database instance. Setting the `depends_on` flag tells docker-compose to start the db container first, any time we run a `web` container, and saves us the step of starting it ourselves in another shell. Signed-off-by: Mike Fiedler <miketheman@gmail.com> * chore(dev): set elasticsearch to single-node The current settings for the elasticsearch container place the started node in "production, single node cluster" mode. This performs boostrap tests, one of which tests for virtual memory via the `sysctl` setting of `vm.max_map_count`. In certain Docker-in-Docker development environments, the end user may not have access to the underlying host settings, and cannot modify this setting. An alternative is to set the `discovery-type` to a single node, placing the service in "development mode", turning any bootstrap checks from errors to warnings. Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/system-config.html#dev-vs-prod Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/bootstrap-checks.html Originally reported in #1511, related to #4370 Signed-off-by: Mike Fiedler <miketheman@gmail.com> * chore: enable context reporting in coverage coverage.py version 5.0 introduced the notion of measurement contexts. This adds details to the report to show: - how many times a given line was executed - which context executed a given line Enabling dynamic context measurement during the test execution adds test class/function contexts to the coverage data to be displayed on a given report output. Refs: https://coverage.readthedocs.io/en/6.3.2/contexts.html#dynamic-contexts Signed-off-by: Mike Fiedler <miketheman@gmail.com> * chore(dev): enable web port to be set via env var Creating a port under 1024 often requires superuser privileges. In some environments this is disallowed. By using the built-in behavior from Docker Compose, a user can now set: WEB_PORT=8080 make serve and the web application will be made availabel on port 8080. The default remains port 80. Signed-off-by: Mike Fiedler <miketheman@gmail.com>
* chore(dev): set web to depend on db When running `make tests`, the current expectation is that the user has executed `make serve` and the database container is running in already. This brings in all the other runtime dependencies, when all the tests need is a running database instance. Setting the `depends_on` flag tells docker-compose to start the db container first, any time we run a `web` container, and saves us the step of starting it ourselves in another shell. Signed-off-by: Mike Fiedler <miketheman@gmail.com> * chore(dev): set elasticsearch to single-node The current settings for the elasticsearch container place the started node in "production, single node cluster" mode. This performs boostrap tests, one of which tests for virtual memory via the `sysctl` setting of `vm.max_map_count`. In certain Docker-in-Docker development environments, the end user may not have access to the underlying host settings, and cannot modify this setting. An alternative is to set the `discovery-type` to a single node, placing the service in "development mode", turning any bootstrap checks from errors to warnings. Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/system-config.html#dev-vs-prod Refs: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/bootstrap-checks.html Originally reported in pypi#1511, related to pypi#4370 Signed-off-by: Mike Fiedler <miketheman@gmail.com> * chore: enable context reporting in coverage coverage.py version 5.0 introduced the notion of measurement contexts. This adds details to the report to show: - how many times a given line was executed - which context executed a given line Enabling dynamic context measurement during the test execution adds test class/function contexts to the coverage data to be displayed on a given report output. Refs: https://coverage.readthedocs.io/en/6.3.2/contexts.html#dynamic-contexts Signed-off-by: Mike Fiedler <miketheman@gmail.com> * chore(dev): enable web port to be set via env var Creating a port under 1024 often requires superuser privileges. In some environments this is disallowed. By using the built-in behavior from Docker Compose, a user can now set: WEB_PORT=8080 make serve and the web application will be made availabel on port 8080. The default remains port 80. Signed-off-by: Mike Fiedler <miketheman@gmail.com>
After clearing up my system on all docker-container, docker images and updating almost everything,
a make initdbgive me the following:Though warehouse seem to work.
That's on MacOS if it changes anything.
The text was updated successfully, but these errors were encountered: