iris-linux-docker

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.

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.

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.

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.

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.

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.