Skip to content

Docker Desktop 4.2.0 Volume DATA view Save As option breaks  #12407

Closed

Description

@jsolderitsch
  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID:73F7948D-CD00-4E52-ACBF-A63554AA4A3C/20211129205438

Actual behavior

I can no longer use the Save As feature from the DATA view of a Docker Volume to export (save as) a file from a Docker container that has the volume associated with it. This behavior started when I had a file path that had a space character in the name. Before I tried this name style, the Save As option from the DATA view worked.

I see a Red Striped error message:

Cannot destructure property 'filepath' of '(intermediate value)' as it is undefined

Now, even when the file path to which I want to Save As the file to does NOT have a space in it, I can't Save as the file. I get the same error message.

Expected behavior

The Save As option from the Docker Desktop Volume DATA view should work as it did originally. I should not see an error message,

Information

  • Windows Version: 20H2 (OS Build 19042.1348)
  • Docker Desktop Version: Docker Desktop 4.2.0
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Steps to reproduce the behavior

Actually, the file path with a space character is not an issue. This is a problem with 4.2.0 in general...

  1. Create a Windows filepath where one of the folders on the path has a space character in the name. (NOT NECESSARY)
  2. Use the Save As... option to try and export a file from a container that has the volume associated with it.
  3. See the error as attached.

Screen Shot 2021-11-29 at 4 09 03 PM

Activity

  1. jsolderitsch commented on Nov 29, 2021

    @jsolderitsch
    Author

    I removed my entire Docker Desktop install and then re-installed it and recreated the volume and container where I met the error. I expected that I then could use Save As... again from the Desktop Volume data view as long as there were no space characters on the file path. I was WRONG. I still get the filepath error. WTF.

  2. jsolderitsch commented on Nov 29, 2021

    @jsolderitsch
    Author

    I am also running Docker Desktop 4.2.0 on my Mac (running Big Sur). This is an Intel Mac Powerbook.

    The Save As option was running just fine there from the DATA view of the Volume interface. Now I am getting the same error there too.
    Screen Shot 2021-11-29 at 5 11 38 PM

  3. jsolderitsch commented on Nov 29, 2021

    @jsolderitsch
    Author

    I am no longer sure that a file path with a space character on it is needed to provoke the problem. Perhaps it's version 4.2.0 in general?

  4. jsolderitsch commented on Nov 29, 2021

    @jsolderitsch
    Author

    On the PC, I reverted to Docker Desktop 4.1.1 and the Save As problem goes away. Even when there is a space character on the path. I am going to change the issue title if I can. Can't change the issue title. This is a general 4.2.0 bug it would seem.

  5. jsolderitsch commented on Nov 30, 2021

    @jsolderitsch
    Author

    The auto-assigned label is wrong -- it should be version/4.2.0

  6. StefanScherer commented on Nov 30, 2021

    @StefanScherer
    Member

    Thanks @jsolderitsch for the report. I can reproduce it even without spaces in the path. We're looking into it.

  7. changed the title [-]Docker Desktop Volume DATA view Save As option breaks after using file path with a space character on the path[/-] [+]Docker Desktop 4.2.0 Volume DATA view Save As option breaks [/+] on Nov 30, 2021
  8. PanopticaRising commented on Dec 2, 2021

    @PanopticaRising

    Workaround, if anyone needs it, seems to be to access your volume directly: \\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes

  9. trungutt commented on Dec 2, 2021

    @trungutt

    @jsolderitsch The new release 4.3.0 is out and has a fix with it

  10. docker-robott commented on Jan 1, 2022

    @docker-robott
    Collaborator

    Closed issues are locked after 30 days of inactivity.
    This helps our team focus on active issues.

    If you have found a problem that seems similar to this, please open a new issue.

    Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
    /lifecycle locked

  11. locked and limited conversation to collaborators on Jan 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions