Can not initialize container – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch fails to initialize its container due to issues like insufficient memory, incorrect configuration settings, or incompatible Java versions. To resolve this, you can increase the memory allocation, check and correct the Elasticsearch configuration settings, or ensure that the Java version installed is compatible with your Elasticsearch version. Additionally, check the Elasticsearch logs for more specific error messages that can guide you to the root cause of the problem.

This guide will help you check for common problems that cause the log ” can not initialize container [{}]: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-azure, container, plugins, repositories and repository-azure.

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();