Why is access to the path /app/ocelot.json denied?

[MuhammadAshouri]

I'm using ocelot in dotnet 8
Running app on windows (self host) is totally fine
But when I run app in docker container I'm getting access denied in AddJsonFile
I've checked container folders and /app/ocelot.json is present (but it's read-only)

Here is my Program.cs

builder.Configuration
    .SetBasePath(environment.ContentRootPath).AddJsonFile("ocelot.json", false, true)
    .AddOcelot(environment)
    .AddEnvironmentVariables();
builder.Services
    .AddOcelot(configuration);

and even when I'm trying to remove read-only attribute I'm getting the same error

var file = new FileInfo("ocelot.json")
{
    IsReadOnly = false
};
file.CopyTo(Path.Combine(environment.ContentRootPath, "ocelot.json"), true);

I've already checked issues and haven't find the solution except this #1216 which seems like it isn't finished yet

Specifications

• Version: 22.0.1
• Platform: Docker (WSL)
• Subsystem: Windows

[raman-m]

Hi Muhammad!
Welcome to Ocelot world! 🐯

I can't get it, is it a bug or do you ask the question "How to configure"?
What I see now is misconfiguration issue... Your Program.cs code is very short!

Please upload whole solution to GitHub for review, or attach more artifacts: JSON config, Ocelot Startup C# code, and Ocelot app logs with errors/exceptions.
Configuration feature docs:

• Configuration, you have to read all subsections carefully
• Routing, it helps to write correct route definition JSON

---

But when I run app in docker container I'm getting access denied in AddJsonFile

Yeap, setup of Docker environment is out of the scope of Ocelot. But, I agree that we don't have much documentation on how to properly run Ocelot in a Docker environment: Search for "docker".
Seems, we need to write more documentation for Docker. But for now, you could refer to Microsoft Learn docs looking for Kestrel & Docker articles.

---

I've checked container folders and /app/ocelot.json is present (but it's read-only)

This is Linux OS in Docker environment issue (WSL is Linux, aka Ubuntu Linux build). Please refer to Linux or Ubuntu documentation, or read more docs for WSL setup.
If you will still be sure that this Ocelot issue when can't write Ocelot file to Linux OS drive then let us know how we could fix this.

[MuhammadAshouri]

I know the config is totally fine because it works perfectly on self-host dotnet in windows (so it cannot be ocelot's bug)
the weirdest thing is that if I mount ocelot.json file in docker compose file it works fine in docker too
(Still I'm pretty sure that ocelot.json is present in container without mounting)
Here is my docker compose (apiGateway section):

apiGateway:
        image: ghcr.io/..../apigateway:latest
        restart: always
        container_name: apiGateway
        ports:
            - "9999:443"
        volumes:
            - ./ocelot.json:/app/ocelot.json

and I know that mounting such a file is terrible in production, so I asked this question

[raman-m]

We are not Docker DevOps team... You need to go to Docker community websites and ask "How to mount file system artifacts to ASP.NET app".

[raman-m]

@MuhammadAshouri

I've already checked issues and haven't find the solution except this #1216 which seems like it isn't finished yet

Regarding #1216 and the Config in-Memory feature... 🆗 We can prioritize this feature...
Would you like to include this to the next release to have the feature in NuGet package v24.0 ?

In any case, having this feature doesn't mean all your DevOps problems with Docker and virtual environments will go away... Do you understand that?

[MuhammadAshouri]

Yeah I do know that it won't fix it all but still the Access Denied error won't happen at least

[raman-m]

OK I added the Feb'24 label on Feb 23
We will try to deliver the #1216 feature in Feb'24 release...

[raman-m]

❗The feature has been merged to develop in commit 84bd6e4 on March 15, 2024

@MuhammadAshouri You can compile develop version and attach to your project. Release will be later...