Claude Code
storage
File Write Operations Failing with Permission Errors
Your application fails when trying to write files to disk, throwing EACCES, EPERM, or permission denied errors. File uploads, log writing, cache storage, or report generation all fail because the application process doesn't have write access to the target directories.
This commonly happens when Claude Code generates code that writes to absolute paths like /tmp, /var, or the project root directory, but the deployment environment (Docker container, cloud function, or restricted server) doesn't allow writes to those locations.
The code works perfectly in local development where you run as an admin user, but breaks immediately in production where the application runs as a restricted service account.
Error Messages You Might See
Error: EACCES: permission denied, open '/var/data/output.pdf'
EPERM: operation not permitted, mkdir '/app/uploads'
OSError: [Errno 13] Permission denied: '/opt/data/cache'
Read-only file system
Common Causes
- Hardcoded absolute paths — Code writes to /tmp or /var/data which may be read-only in containerized environments
- Read-only filesystem in serverless — Cloud functions and some container runtimes have read-only root filesystems
- Docker container running as non-root — The application user inside the container doesn't own the target directory
- Missing directory creation — Code tries to write a file before creating its parent directory
- SELinux or AppArmor restrictions — Security modules blocking file writes even when Unix permissions allow them
How to Fix It
- Use os.tmpdir() or platform-agnostic paths — Replace hardcoded paths with Node's os.tmpdir() or Python's tempfile.gettempdir()
- Create directories before writing — Always call fs.mkdirSync(dir, {recursive: true}) or os.makedirs(dir, exist_ok=True) before file operations
- Use /tmp in serverless — In AWS Lambda or similar, /tmp is the only writable directory. Configure your app to use it
- Set correct Docker permissions — Add RUN chown -R appuser:appuser /app/data in your Dockerfile for writable directories
- Use object storage for production — Replace local file writes with S3, GCS, or Supabase Storage for production deployments
Real developers can help you.
Jacek Rozanski
Senior PHP/Symfony developer and DevOps engineer with 20+ years of professional experience, running opcode.pl (web development agency, est. 2004).
Day job: I'm the sole backend developer at merketing company where I own and maintain 11 PHP/Symfony microservices on AWS (ECS Fargate, RDS, S3, CloudFront), handle the full CI/CD pipeline (Bitbucket Pipelines, Docker), and manage monitoring with Sentry and CloudWatch. These services handle high request volumes in production every month.
What I bring to AI-built apps:
- I audit and fix security issues (OWASP methodology), performance bottlenecks, and architectural problems in codebases generated by Cursor, Claude Code, Lovable, Bolt, and v0
- I refactor AI-generated prototypes into production-grade applications with proper error handling, testing, and clean architecture (SOLID, DDD, hexagonal architecture)
- I set up the infrastructure AI tools don't touch: AWS hosting, CI/CD pipelines, automated deployments, database optimization, monitoring, and alerting
- I integrate external services: payment providers, email systems, partner APIs, SSO/auth
Tech stack: PHP 8.x, Symfony, React, Next.js, PostgreSQL, MySQL, Docker, AWS (ECS, RDS, S3, SQS/SNS, CloudFront), Terraform, Supabase. I also use AI tools daily (Claude Code, Cursor) in my own workflow, so I understand both the strengths and the gaps in AI-generated code.
Based in Poland (CET timezone). Available for async work and calls during EU/US business hours.
Matthew Butler
Systems Development Engineer @ Amazon Web Services
ISHANTDEEP SINGH
Senior Software Engineer with 7+ years of experience in React, JavaScript, TypeScript, Next.js, and Node.js. I’ve also worked as a tech lead for startups, owning end-to-end technical execution including architecture, development, scaling, and delivery. I bring a strong mix of hands-on coding, product thinking, and technical leadership, and I’m comfortable building products from scratch as well as improving and scaling existing systems.
Pratik
SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure
BurnHavoc
Been around fixing other peoples code for 20 years.
legrab
I'll fill this later
Prakash Prajapati
I’m a Senior Python Developer specializing in building secure, scalable, and highly available systems. I work primarily with Python, Django, FastAPI, Docker, PostgreSQL, and modern AI tooling such as PydanticAI, focusing on clean architecture, strong design principles, and reliable DevOps practices. I enjoy solving complex engineering problems and designing systems that are maintainable, resilient, and built to scale.
Franck Plazanet
I am a Strategic Engineering Leader with over 8 years of experience building high-availability enterprise systems and scaling high-performing technical teams. My focus is on bridging the gap between complex technology and business growth.
Core Expertise:
🚀 Leadership: Managing and coaching teams of 15+ engineers, fostering a culture of accountability and continuous improvement.
🏗️ Architecture: Enterprise Core Systems, Multi-system Integration (ERP/API/ETL), and Core Database Structure.
☁️ Cloud & Scale: AWS Expert; architected systems handling 10B+ monthly requests and managing 100k+ SKUs.
📈 Business Impact: Aligning tech strategy with P&L goals to drive $70k+ in monthly recurring revenue.
I thrive on "out-of-the-box" thinking to solve complex technical bottlenecks and am always looking for ways to use automation to improve business productivity.
Bastien Labelle
Full stack dev w/ 20+ years of experience
Mehdi Ben Haddou
- Founder of Chessigma (1M+ users) & many small projects
- ex Founding Engineer @Uplane (YC F25)
- ex Software Engineer @Amazon and @Booking.com
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Why does file writing work locally but not in production?
Local development typically runs as your user with full permissions. Production environments (Docker, serverless, cloud VMs) run as restricted users with limited filesystem access. Always use platform-appropriate writable directories.
Where can I write files in AWS Lambda?
Only the /tmp directory is writable in Lambda, with a 512MB limit (configurable up to 10GB). For persistent storage, upload to S3 instead of writing locally.