-
Notifications
You must be signed in to change notification settings - Fork 19
Getting Internal server error
when trying to export to Windows network volume
#108
Comments
@Bassadin, I'm also experiencing an Internal server error when trying to use this extension, although i'm using Mac so I don't know if we're experiencing the same issue. I wanted to share a command I found to show the logs for this extension - I thought perhaps this might help you get more details about your issue that you can add to your issue report here. to show the extension logs, run |
I got this, if it helps:
|
Your error seems to be related with incorrect Windows export path handling on docker. I am working on Docker Desktop for Linux. |
I get the same error. I checked the logs and I see this entry. Is it supposed to say
WSL Info
Docker Desktop Info
|
Having the same issue and there's no work around that I can think of. Running windows docker desktop you have to select a windows file system folder. You can try selecting a linux drive but you still get same error. I can't see how export to file can work on Windows with WSL2 |
The only workaround is to use the Volumes workspace/area in Docker Desktop: Volumes > [Select a Volume] > Exports tab > Quick Export Quick Export is the same UI as the extension and it works. Seems like a simple typo in the Extension is trying to "vackup", not "backup" the volumes. @simon-mottram-cucumber hopefully this helps for now |
Describe the bug
When trying to export a volume to a Windows network volume, I get an Error message
Add the steps to reproduce
Steps to reproduce the behavior:
Export volume
Describe the expected behavior
Got the error:
Failed to backup volume ttn-locator-backend_postgres-data to \\Orzhova\home\Drive\Backups\Master-Thesis-INM\ttn-locator-db: {"message":"Internal Server Error"}. HTTP status code: 500
Optional: Add screenshots
Output of
docker extension version
:Output of
docker version
:Include extension console logs
No log gets output in the chrome debugger view, sadly
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: