You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In FileBuilder, when RenderDockerfile gets called, it always renderes a Dockerfile to the _workingFolder with the name of "Dockerfile".
When multiple Docker containers is build simultaneous, this means that the file gets overwritten multiple times, and often results in some FluentDocker Fd services locking the file and reading from other instances.
A solution could be to allow for a TemplateString input for a private config field, fx private TemplateString _renderedDockerfileName = "Dockerfile".
Then it would be able to set the _renderedDockerfileName to "${RND}", and thus solve the problem.
A separate problem is that the file isn't cleaned up after use. In my usecase, it's frustrating with multiple projects and multiple runs that it generates an extra Dockerfile at the working folder, when I already have "Service1.Dockerfile" and "Service2.Dockerfile". But this is a seperate issue, even though it would make custom rendered Dockerfile names a lot easier to manage.
The text was updated successfully, but these errors were encountered:
Hi there. I sadly was not able to fix this issue in the following PR: #248
If this issue should be closed, then please, feel free to.
I sadly do not work with C# anymore, so I lack the motivation for doing this :(
In FileBuilder, when RenderDockerfile gets called, it always renderes a Dockerfile to the _workingFolder with the name of "Dockerfile".
When multiple Docker containers is build simultaneous, this means that the file gets overwritten multiple times, and often results in some FluentDocker Fd services locking the file and reading from other instances.
A solution could be to allow for a TemplateString input for a private config field, fx private TemplateString _renderedDockerfileName = "Dockerfile".
Then it would be able to set the _renderedDockerfileName to "${RND}", and thus solve the problem.
A separate problem is that the file isn't cleaned up after use. In my usecase, it's frustrating with multiple projects and multiple runs that it generates an extra Dockerfile at the working folder, when I already have "Service1.Dockerfile" and "Service2.Dockerfile". But this is a seperate issue, even though it would make custom rendered Dockerfile names a lot easier to manage.
The text was updated successfully, but these errors were encountered: