---
name: containers-ts-storage-object-ownership-mountpath
title: Why can't the ownership of the mount path be changed?
description: '[Virtual Private Cloud] [Classic infrastructure]'
last-updated: 2026-04-29
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why can't the ownership of the mount path be changed?
{: #cos_mountpath_error}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}



You created a deployment that mounts an IBM Cloud Object Storage bucket to your app. During the deployment, you try to change the ownership of the volume mount path, but this action fails. You see error messages similar to the following examples.
{: tsSymptoms}

```sh
chown: changing ownership of '<volume_mount_path>': Input/output error
chown: changing ownership of '<volume_mount_path>': Operation not permitted
```
{: screen}

When you create a bucket in IBM Cloud Object Storage, the bucket is managed by `s3fs-fuse`. The UID and GID that own the volume mount path are automatically set by Fuse when you mount the bucket to your app and can't be changed.
{: tsCauses}

You can't change the ownership of the volume mount path. However, you can change the UID and GID for a file or directory that is stored under your volume mount path. For more information, see [Object storage: Accessing files with a non-root user fails](https://cloud.ibm.com/docs/containers?topic=containers-cos_nonroot_access&format=markdown).
{: tsResolve}