Cannot access in container – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.2

Briefly, this error occurs when Elasticsearch cannot access its data or configuration files within a Docker container. This could be due to incorrect file permissions, incorrect path configuration, or the container not running properly. To resolve this issue, you can check and correct file permissions, ensure the correct path is set in the Elasticsearch configuration, or restart the Docker container. Additionally, ensure that the Elasticsearch process inside the container is running with the correct user privileges.

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

Log Context

Log “cannot access [{}] in container {{}}: {}” classname is
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);



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?