Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Read Only file system on Linux containers

See original GitHub issue

Hi,

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 GitHub Comments

2reactions

karolz-mscommented, Aug 20, 2018

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

1reaction

karolz-mscommented, Aug 21, 2018

@mikehole EventFlow Core package 1.4.4, just published on Nuget, should fix this problem. Please test and let me know what you find!

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...

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...

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-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 ...

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...