depl0y

Update time: I finally gave up and opened an account at a Docker hosting service. When running my docker there, I also received an exception, but there the exception was a lot more descriptive: Unhandled Exception: System.UnauthorizedAccessException: Access to the path '/proc/1/map_files' is denied. ---> System.IO.IOException: Operation not permitted, at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.TryEnableFileSystemWatcher(), at System.IO.FileSystemWatcher.RunningInstance..ctor(FileSystemWatcher watcher, SafeFileHandle inotifyHandle, String directoryPath, Boolean includeSubdirectories, NotifyFilters notifyFilters, CancellationToken cancellationToken), at System.IO.FileSystemWatcher.RunningInstance.AddDirectoryWatchUnlocked(WatchedDirectory parent, String directoryName), at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed(), at System.IO.FileSystemWatcher.StartRaisingEvents(), at System.IO.FileSystemWatcher.set_EnableRaisingEvents(Boolean value), at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.CreateFileChangeToken(String filter), at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer), at Microsoft.Extensions.Configuration.FileConfigurationProvider..ctor(FileConfigurationSource source), at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors), at ChangeCore.Program.Main(String[] args) in F:\ChangeCore\ChangeCore\Program.cs:line 17, at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build(), at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build(), at Microsoft.Extensions.Configuration.Json.JsonConfigurationSource.Build(IConfigurationBuilder builder), at System.IO.Enumeration.FileSystemEnumerator`1.FindNextEntry(), at System.IO.Enumeration.FileSystemEnumerator`1.MoveNext(), --- End of inner exception stack trace --- Googling that message gave me the following github issue: https://github.com/dotnet/dotnet-docker/issues/485 It seems that since a certain version of Docker, it seems necessary to add a WORKDIR to the Dockerfile, which I only did for the building of the application and not the running. So, problem solved.

I am a C# developer which runs Unraid at home. I use docker on Unraid to (for example) run an API so that I can test some stuff, but ever since the fixes for the SQLite corruption (not related, but for time frame, I think version 6.8 ?) my Docker can not start .netcore projects anymore. I have been debugging this for the last couple of days now, but in the end it seems that even the most basic empty project causes the same exceptions. Unhandled exception. System.IO.IOException: Input/output error at System.IO.Enumeration.FileSystemEnumerator`1.FindNextEntry(Byte* entryBufferPtr, Int32 bufferLength) at System.IO.Enumeration.FileSystemEnumerator`1.MoveNext() at System.IO.FileSystemWatcher.RunningInstance.AddDirectoryWatchUnlocked(WatchedDirectory parent, String directoryName) at System.IO.FileSystemWatcher.RunningInstance.AddDirectoryWatchUnlocked(WatchedDirectory parent, String directoryName) at System.IO.FileSystemWatcher.RunningInstance.AddDirectoryWatchUnlocked(WatchedDirectory parent, String directoryName) at System.IO.FileSystemWatcher.RunningInstance.AddDirectoryWatchUnlocked(WatchedDirectory parent, String directoryName) at System.IO.FileSystemWatcher.RunningInstance..ctor(FileSystemWatcher watcher, SafeFileHandle inotifyHandle, String directoryPath, Boolean includeSubdirectories, NotifyFilters notifyFilters, CancellationToken cancellationToken) at System.IO.FileSystemWatcher.StartRaisingEvents() at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed() at System.IO.FileSystemWatcher.set_EnableRaisingEvents(Boolean value) at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.TryEnableFileSystemWatcher() at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.CreateFileChangeToken(String filter) at Microsoft.Extensions.FileProviders.PhysicalFileProvider.Watch(String filter) at Microsoft.Extensions.Configuration.FileConfigurationProvider.<.ctor>b__1_0() at Microsoft.Extensions.Primitives.ChangeToken.ChangeTokenRegistration`1..ctor(Func`1 changeTokenProducer, Action`1 changeTokenConsumer, TState state) at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer) at Microsoft.Extensions.Configuration.FileConfigurationProvider..ctor(FileConfigurationSource source) at Microsoft.Extensions.Configuration.Json.JsonConfigurationSource.Build(IConfigurationBuilder builder) at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build() at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration() at Microsoft.Extensions.Hosting.HostBuilder.Build() at UnraidFail.Program.Main(String[] args) in /app/UnraidFail/Program.cs:line 16 I also have been testing this, running Docker on my Macbook, where the Docker I created for this, runs without a hitch. (source code here: https://git.x77.nl/depl0y/UnraidFail/src/branch/master ). In that repository is a Dockerfile that can be used to test this. It downloads the source of that repository to the Docker itself, compiles it and creates a runnable application. The application is actually an example project from Visual Studio itself. I cannot downgrade to an earlier version of Unraid, because that will break my Plex and Sonarr. I also tried upgrading to the latest 6.9.0-beta1 version, but that didn't help either. I know this is a very specific case and googling for anything like this results in nothing usable. Maybe someone can try running this, so I know it isn't my Unraid install? titan-diagnostics-20200609-0714.zip

I recently updated to 6.7.3-rc4 (and docker data is on a single disk). What I have noticed is that Plex is running without problems at the moment. Sonarr is a weird beast though, it's still going corrupt. Something I noticed is that after restoring a backup, that Sonarr could get back up, but in the logs still complain about database corruption. I wonder if my Sonarr problems on 6.7.3-rc4 could be that I should just start from 0 with that database. Restoring a backup might not give me a fully working database, because I don't know where the smallest corruption started and I have tons of backups, but most of them are from the 6.7.2 install and earlier (where docker data was still on multiple disks).

I am having the same problem, with a clean VM running Windows 10 under Unraid 6.7.1-rc1. Every game (until now) worked like it should, while RoE straightout just banned me when first starting the game. Mind you, I haven't started the game before on another PC or anything. I also tried adding the following to the configuration of my VM (I read it somewhere), that would hide the fact that I am running a VM from the Guest OS: <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,hv_time,kvm=off,hv_vendor_id=null,-hypervisor'/> </qemu:commandline> After adding that, restarting, it removed the code, so there probably is a problem with that. As I just copied and pasted it, that might be.