Skip to navigation Skip to main content

Search

Content extracted on: 2026-09-15

Home
Product Documentation
Red Hat OpenShift Dev Spaces
3.30
Configure fuse-overlayfs
Configure fuse-overlayfs

What's new

Red Hat OpenShift Dev Spaces release notes
Technology Preview

Discover

What is OpenShift Dev Spaces?
What problems does OpenShift Dev Spaces solve?
Who is OpenShift Dev Spaces for?
When to use OpenShift Dev Spaces
How OpenShift Dev Spaces works
Common user roles and tasks

Get Started

Prepare the platform for developers
Create your first cloud workspace
Connect to your Git repositories
1. How Git authentication works in cloud development environments
2. Access private repositories with a personal access token

Plan

Plan deployment resources

Install

How the installation works
1. Permissions required for CLI installation
2. Permissions required for web console installation
Install Red Hat OpenShift Dev Spaces
Confirm OpenShift Dev Spaces is running
Get the dashboard URL to share with your team
Prepare OpenShift Dev Spaces for your team
Remove OpenShift Dev Spaces from your cluster

Upgrade

Plan your upgrade
Approve a pending update in the web console
Upgrade from the command line
1. Upgrade by using the dsc management tool
2. Upgrade in an air-gapped environment
Verify the upgrade completed successfully
Fix a duplicate Dev Workspace Operator after a cluster upgrade

Configure

Customize the central configuration
1. How the central configuration works
2. Edit the central configuration from the command line
CheCluster Custom Resource fields reference
Dev Workspace Operator custom resources
Connect server components to enterprise systems
Customize the developer dashboard
1. Customize the dashboard samples for your team
2. Apply your organization’s branding to the dashboard
Use the server API
Organize workspace namespaces
Set workspace policies for all users
Set up network access for workspaces
Control where workspace data is stored
Configure fuse-overlayfs
Back up workspaces
1. Configure backup with the integrated OpenShift registry
2. Configure backup with a regular OCI-compatible registry

Secure

Protect your deployment
Control who can access OpenShift Dev Spaces

Optimize

What you can optimize in OpenShift Dev Spaces
Speed up workspace starts with image caching
Scale the platform automatically
1. Scale OpenShift Dev Spaces for high availability
2. Prevent workspace failures during node scaling
Configure automatic cleanup of inactive workspaces
Disable the workspace CA bundle mount
Disable Copied CSVs to reduce etcd usage
Verify workspace performance after optimization
1. Check replica counts, image cache, and workspace startup

Develop

What development tools you can configure
Choose and configure your IDE
Use AI coding assistants
Persist AI assistant configuration
What you can do in a Cloud Development Environment
Standardize workspace environments
1. Devfile in OpenShift Dev Spaces
2. What you can customize in a Cloud Development Environment
Manage credentials and configurations in workspaces
Build and run containers in workspaces
Collaborate with your team
Persist and restore workspace data
Share preconfigured workspace links with your team

Observe

What you can observe about OpenShift Dev Spaces
Monitor platform health
Configure the Woopra telemetry plugin
Configure logging to isolate issues

Integrate

Connect Git providers with OAuth
Manage workspaces with OpenShift tools
Resolve dependencies in restricted environments

Extend

What you can customize in workspace tooling
Choose which editors are available
Customize the default IDE
Add or remove IDE extensions
Deploy a private extension registry
Enable the managed Open VSX registry
What you can add to your platform
Register AI coding assistants for developers
Build a custom telemetry plugin

Troubleshoot

When something goes wrong with your workspace
View Cloud Development Environment logs
Debug a failing workspace
Diagnose slow workspaces
Fix webview loading errors in private browsing
Fix devfile errors
When something goes wrong with the platform
Diagnose workspace startup failures
Diagnose slow Cloud Development Environments
Troubleshoot network problems
Fix OAuth configuration errors

Download PDF

Red Hat Dev Spaces 3.30 PDF Reference

Configure fuse-overlayfs

Configure fuse-overlayfs for building container images within OpenShift Dev Spaces workspaces. For related container build procedures, see Additional resources.

When to enable fuse-overlayfs
Use the fuse-overlayfs storage driver for Podman and Buildah in the Universal Developer Image (UDI) instead of the default vfs driver, which does not provide copy-on-write support.
Enable /dev/fuse access on OpenShift 4.14 and earlier
Enable /dev/fuse access for workspace containers on OpenShift versions older than 4.15, so that workspaces can use the fuse-overlayfs storage driver for Podman and Buildah.
Enable fuse-overlayfs for all workspaces
Enable fuse-overlayfs for all workspaces to use the overlay storage driver.

Related information

This content is not included.Build and run containers in workspaces

‹ How workspace files persist across restarts
When to enable fuse-overlayfs ›

CONTENT

Product documentation
Knowledgebase
Errata
CVEs
Product life cycles
Security Data API

HELP

Contact Red Hat

APP INFO

About
Release: v1.2.13 2026-09-15

© 2026 Red Hat

End user license agreement