How To Solve Issues Related to Log – Can not initialize container :

How To Solve Issues Related to Log – Can not initialize container :

Updated: Feb-20

Elasticsearch Version: 1.7-8.0


Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.

To troubleshoot log “Can not initialize container :” it’s important to understand a few problems related to Elasticsearch concepts cloud-azure, container, plugins, repositories, repository-azure. See bellow important tips and explanations on these concepts

Log Context

Log”can not initialize container [{}]: [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 if (!blobStore.doesContainerExist(blobStore.container())) {
                    logger.debug("container [{}] does not exist. Creating..."; blobStore.container());
            } catch (StorageException | URISyntaxException e) {
                logger.warn("can not initialize container [{}]: [{}]"; blobStore.container(); e.getMessage());
                throw new RepositoryVerificationException(repositoryName; "can not initialize container " + blobStore.container(); e);
        return super.startVerification();

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 elasticsearch-1.6 Could not initialize class org.elasticsearch.monitor.jvm.JvmInfo when connecting to its docker container 0.18 K 1

How can I run script automatically after Docker container startup   9.88 K 4

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now