Read Only file system on Linux containers
See original GitHub issueHi,
I have been trying to use eventflow within Linux containers but have hit the problem where creating the pipeline (DiagnosticPipelineFactory.CreatePipeline
) it throws up an System.IO.IOException: ‘Read-only file system’ exception.
Not sure if there is there a work around for this or I am going about things in the right way so this may not be an issue.
Cheers,
Mike
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Container root file system is set to read-only
The container's root filesystem should be treated as a 'golden image' by using Docker run's --read-only option. This prevents any writes to the...
Read more >Use Read-Only filesystem for containers where possible
A read-only root filesystem helps to enforce an immutable infrastructure strategy. The container should only write on mounted volumes that can persist, even...
Read more >Docker - mkdir read-only file system
How are you running the container? · read-only file system might indicate hdd failure. · The process is running as a normal user,...
Read more >Read-only filesystems in Docker and Kubernetes
Learn how to make your filesystems in containers read-only to minimize the attack surface and create controlled exceptions using tmpfs and ...
Read more >5.12 Mount container's root filesystem as read only
Add a '--read-only' flag to allow the container's root filesystem to bemounted as read only. This can be used in combination with volumes...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK I think I understand the problem. Seems like a bug in the default health reporter. Hopefully with have a PR with a fix later today
@mikehole EventFlow Core package 1.4.4, just published on Nuget, should fix this problem. Please test and let me know what you find!