# Issue with ‘store is read-only’ in Weaviate Docker Deployment

**URL:** https://forum.weaviate.io/t/issue-with-store-is-read-only-in-weaviate-docker-deployment/3230
**Category:** Support
**Tags:** python, technical
**Created:** [July 31, 2024, 9:30am UTC](https://forum.weaviate.io/t/issue-with-store-is-read-only-in-weaviate-docker-deployment/3230 "2024-07-31T09:30:14Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![fr\_yuan](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/fr_yuan/32/2067_2.png) [@fr\_yuan](https://forum.weaviate.io/u/fr_yuan)
#### Post date: [July 31, 2024, 9:30am UTC](https://forum.weaviate.io/t/issue-with-store-is-read-only-in-weaviate-docker-deployment/3230/1 "2024-07-31T09:30:14Z")

</div>

Hello Weaviate Community,

I am encountering an issue with my Weaviate instance that I deployed using Docker. When attempting to store data, I receive the following error message:  
put object: import into index business10007scene1000704strategy89: put local object: shard=“rbGyIAVZC9Nl”: store is read-only  
I believe this issue is related to the data persistence configuration, but I am not certain. I have taken a proactive step to check the disk usage on the host system and can confirm that it has not reached the 90% threshold, which I understand could be a potential cause for a read-only state.  
Thank you in advance for your help. I am looking forward to your responses.

---

<div class="post-metadata">

### Author: ![Shahin](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/shahin/32/7944_2.png) [@Shahin](https://forum.weaviate.io/u/Shahin)
#### Post date: [July 31, 2024, 12:04pm UTC](https://forum.weaviate.io/t/issue-with-store-is-read-only-in-weaviate-docker-deployment/3230/2 "2024-07-31T12:04:20Z")

</div>

Hello @fr_yuan,

Welcome to our community! It’s great to have you here 😊

The issue is likely due to running out of disk space. However, since you’ve checked and everything seems fine, I suggest setting the shard status to `READY`.

You can find more information on how to do this here:

> **[Manage collections | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/manage-data/collections#update-shard-status)**
>
> Every object in Weaviate belongs to exactly one collection. Use the examples on this page to manage your collections.

This should resolve the issue, but please keep an eye on the disk volume in the meantime.

I hope this helps!