iris-linux-docker

Fix Linux volume permissions for IRIS Docker containers using ACLs, tmpfs, chown, or named volumes.

27|10|Updated Apr 21, 2026

Search Tags:#permissions #docker #linux #startup #iris #bind-mount

Ready to run

npx skills add https://github.com/intersystems-community/iris-dev --skill iris-linux-docker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iris-linux-docker
Source: https://github.com/intersystems-community/iris-dev/tree/main/light-skills/skills/iris-linux-docker
Command: npx skills add https://github.com/intersystems-community/iris-dev --skill iris-linux-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IRIS Docker containers on Linux run as UID 51773 (irisowner). Bind-mounting a host directory owned by a regular Linux user can cause startup failures. This Skill provides guidance and practical options to ensure proper permissions and reliable startup across Linux hosts.

Core Features & Use Cases

Permission fixes: Recommendations for applying POSIX ACLs, tmpfs, chown, or named Docker volumes to ensure irisowner can write to mounted volumes.
Deployment guidance: Applicable to all IRIS editions on Linux (community, enterprise, irishealth, ai_hub).
Startup troubleshooting: Steps to diagnose iris-main.log errors related to bind-mounts and restore startup.

Quick Start

Apply POSIX ACLs to the host directory and restart the IRIS container to ensure irisowner has write access.

Frequently Asked Questions about iris-linux-docker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does my IRIS Docker container fail to start when bind-mounting a host directory on Linux?▼

IRIS Docker containers on Linux run as UID 51773 (irisowner), so bind-mounting a host directory owned by a regular Linux user causes startup failures because irisowner lacks write permissions to the volume.

How do I fix Linux volume permissions for IRIS containers?▼

You can fix Linux volume permissions for IRIS containers by ensuring host directories are writable by UID 51773, applying POSIX ACLs, changing ownership with chown, using tmpfs, or switching to named Docker volumes.

What is the best way to grant irisowner write access to bind-mounted volumes?▼

Applying POSIX ACLs to the host directory is a recommended approach to grant irisowner write access to bind-mounted volumes without changing the base ownership, ensuring reliable IRIS container startup.

Does this permission fix apply to all IRIS editions on Linux?▼

Yes, these deployment guidelines and permission fixes apply to all IRIS editions on Linux, including community, enterprise, irishealth, and ai_hub, ensuring irisowner can write to mounted volumes.

How do I troubleshoot iris-main.log startup errors related to bind-mounts?▼

To troubleshoot iris-main.log startup errors, diagnose the bind-mount permission failures, apply the recommended permission mitigations like ACLs or chown for UID 51773, and restart the IRIS container.

When should I use named Docker volumes instead of bind-mounts for IRIS?▼

You should use named Docker volumes instead of bind-mounts for IRIS when you want to avoid host directory ownership conflicts entirely, as Docker manages named volumes and ensures irisowner has the required write permissions.