Unable to start Docker container according to documentation
See original GitHub issue
[ajung@vmd16513 ~]$ docker run crate
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2019-03-07 16:56:38,942 main ERROR ThresholdFilter contains an invalid element or attribute "onMismatch"
2019-03-07 16:56:38,981 main ERROR ThresholdFilter contains an invalid element or attribute "onMismatch"
[2019-03-07T16:56:39,001][WARN ][o.e.c.l.LogConfigurator ] [unknown] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace `%node_name` with `[%node_name]%marker ` in these locations:
/crate/config/log4j2.properties
2019-03-07 16:56:39,722 main ERROR ThresholdFilter contains an invalid element or attribute "onMismatch"
2019-03-07 16:56:39,729 main ERROR ThresholdFilter contains an invalid element or attribute "onMismatch"
[2019-03-07T16:56:39,736][WARN ][o.e.c.l.LogConfigurator ] [Petzeck] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace `%node_name` with `[%node_name]%marker ` in these locations:
/crate/config/log4j2.properties
[2019-03-07T16:56:40,079][INFO ][o.e.e.NodeEnvironment ] [Petzeck] using [1] data paths, mounts [[/data (/dev/sda2)]], net usable_space [487.1gb], net total_space [599.2gb], types [xfs]
[2019-03-07T16:56:40,080][INFO ][o.e.e.NodeEnvironment ] [Petzeck] heap size [494.9mb], compressed ordinary object pointers [true]
[2019-03-07T16:56:40,081][INFO ][o.e.n.Node ] [Petzeck] node name [Petzeck], node ID [zeda_N-4RxuL6JDJGYCobA]
[2019-03-07T16:56:40,109][INFO ][o.e.n.Node ] [Petzeck] version[3.2.4], pid[1], build[1be62d9/2019-02-25T12:21:06Z], OS[Linux/4.16.11-100.fc26.x86_64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/11.0.1/11.0.1+13]
[2019-03-07T16:56:40,110][INFO ][o.e.n.Node ] [Petzeck] JVM arguments [-Xms512M, -Xmx512M, -Djava.awt.headless=true, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -Xlog:gc*,gc+age=trace,safepoint:file=/data/log/gc.log:utctime,pid,tags:filecount=16,filesize=64m, -XX:+DisableExplicitGC, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/data/data, -XX:+UnlockExperimentalVMOptions, -Des.cgroups.hierarchy.override=/]
[2019-03-07T16:56:40,609][INFO ][i.c.plugin ] [Petzeck] plugins loaded: [hyperLogLog, jmx-monitoring, lang-js]
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[2019-03-07T16:56:41,885][INFO ][o.e.p.PluginsService ] [Petzeck] no modules loaded
[2019-03-07T16:56:41,887][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [crate-azure-discovery]
[2019-03-07T16:56:41,887][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [es-repository-hdfs]
[2019-03-07T16:56:41,887][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [io.crate.plugin.BlobPlugin]
[2019-03-07T16:56:41,887][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [io.crate.plugin.CrateCorePlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [io.crate.plugin.HttpTransportPlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [io.crate.plugin.LicensePlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [io.crate.plugin.PluginLoaderPlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [io.crate.plugin.SrvPlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [io.crate.udc.plugin.UDCPlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [org.elasticsearch.analysis.common.CommonAnalysisPlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [org.elasticsearch.discovery.ec2.Ec2DiscoveryPlugin]
[2019-03-07T16:56:41,888][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [org.elasticsearch.plugin.repository.url.URLRepositoryPlugin]
[2019-03-07T16:56:41,889][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [org.elasticsearch.repositories.s3.S3RepositoryPlugin]
[2019-03-07T16:56:41,889][INFO ][o.e.p.PluginsService ] [Petzeck] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
[2019-03-07T16:56:43,681][INFO ][o.e.d.DiscoveryModule ] [Petzeck] using discovery type [zen] and host providers [settings]
[2019-03-07T16:56:45,206][INFO ][i.c.p.ssl ] [Petzeck] HTTP SSL support is disabled.
[2019-03-07T16:56:46,197][INFO ][o.e.n.Node ] [Petzeck] initialized
[2019-03-07T16:56:46,201][INFO ][o.e.n.Node ] [Petzeck] starting ...
[2019-03-07T16:56:46,420][INFO ][psql ] [Petzeck] PSQL SSL support is disabled.
[2019-03-07T16:56:46,842][INFO ][psql ] [Petzeck] publish_address {172.17.0.8:5432}, bound_addresses {127.0.0.1:5432}, {172.17.0.8:5432}
[2019-03-07T16:56:46,927][INFO ][i.c.p.h.CrateNettyHttpServerTransport] [Petzeck] publish_address {172.17.0.8:4200}, bound_addresses {127.0.0.1:4200}, {172.17.0.8:4200}
[2019-03-07T16:56:46,996][INFO ][o.e.t.TransportService ] [Petzeck] publish_address {172.17.0.8:4300}, bound_addresses {127.0.0.1:4300}, {172.17.0.8:4300}
[2019-03-07T16:56:47,065][INFO ][o.e.b.BootstrapChecks ] [Petzeck] bound or publishing to a non-loopback address, enforcing bootstrap checks
ERROR: [1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2019-03-07T16:56:47,097][INFO ][o.e.n.Node ] [Petzeck] stopping ...
[2019-03-07T16:56:47,296][INFO ][o.e.n.Node ] [Petzeck] stopped
[2019-03-07T16:56:47,296][INFO ][o.e.n.Node ] [Petzeck] closing ...
[2019-03-07T16:56:47,316][INFO ][o.e.n.Node ] [Petzeck] closed
Specifying a port mapping using -p
does not make a difference.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Workarounds for common problems - Docker Documentation
Docker Desktop fails to start when anti-virus software is installed . Some anti-virus software may be incompatible with Hyper-V and Microsoft Windows...
Read more >docker run - Docker Documentation
The docker run command first creates a writeable container layer over the specified image, and then starts it using the specified command. That...
Read more >Troubleshoot topics | Docker Documentation
If you are using mounted volumes and get runtime errors indicating an application file is not found, access to a volume mount is...
Read more >Start containers automatically - Docker Documentation
The following example starts a Redis container and configures it to always restart unless it is explicitly stopped or Docker is restarted.
Read more >Troubleshoot Docker Engine installation
Docker can't run correctly if your kernel is older than version 3.10, or if it's missing kernel modules. To check kernel compatibility, you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The documentation is in general correct.
Perhaps add
sysctl -w vm.max_map_count=262144
explicitly to the documentation and mention that it applies also to the Docker host. Perhaps I was under the impression that this configuration applies to settings of the Docker image itself.Thanks @zopyx, after run the below code, it solves the issue on my VM: