-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blazor Server running in docker container cant access static web assets #82
Comments
Hello, I'm sorry but I am really a docker novice so I'm of little help. Try reading this thread to see if you can get something out of it. That said, staticwebassets are not needed for the component to run server-side if you use the initializeonfirstcall=true option, so if you could just get rid of it somehow that could be a workaround |
Are you using any other package that has staticwebassets that works? That could help me compare in case my packaging setup has some kind of issue. |
Is this not happening for you? |
The assets are there in the container. All fine. It looks like this is only related if the docker container is started via visual studio. If the created container is manually started via docker run, all is working. So the error can be scoped to the visual studio starting/debugging experience which is not working. The package in general is working when container is started manually. Thanks for you great work! I think this can be closed as it is related to visual studio and container debugging only. |
OK thanks for the feedback, closing |
Describe the bug
Building an blazor app server-side with FileReader works without any problem. When deploying as docker container, startup fails as it wants to access "/root/.nuget/packages/tewr.blazor.filereader/0.15.0.19248/staticwebassets" during first run, which is not mounted as a volume.
Error message
Project type
Server-side
Environment
What might be a solution to avoid this error and to avoid mounting as a volume as this is not available on client environments? Should I include the static assets directly in the source folder?
The text was updated successfully, but these errors were encountered: