Can not access container – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to access a specific container, possibly due to network issues, incorrect permissions, or the container not running. To resolve this, ensure the container is running and accessible. Check the network settings and permissions. If the container is running on Docker, use Docker commands to inspect the container’s status. Also, verify the Elasticsearch configuration to ensure it’s correctly set to access the container. Lastly, check the logs for any specific issues that might be causing this error.

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

Log Context

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

         try {
            CloudBlobClient client = this.getSelectedClient(account; mode);
            CloudBlobContainer blob_container = client.getContainerReference(container);
            return blob_container.exists();
        } catch (Exception e) {
            logger.error("can not access container [{}]"; container);
        return false;



How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?