Log Cannot access in container : – How To Solve Related Issues

Log Cannot access in container : – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

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

Log Context

Log”Cannot access [{}] in container {{}}: {}” classname is AzureBlobStore.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     public void delete(BlobPath path) throws IOException {
        final String keyPath = path.buildAsString();
        try {
            service.deleteFiles(clientName; container; keyPath);
        } catch (URISyntaxException | StorageException e) {
            logger.warn("cannot access [{}] in container {{}}: {}"; keyPath; container; e.getMessage());
            throw new IOException(e);


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 cannot access elasticsearch in docker for windows linux containers

0.43 K 1

Unable to access kibana web UI and Elasticsearch running in docker container from host machine

  0.17 K

Running elasticsearch on Azure VM using Docker: cannot access via localhost


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now