Describe the bug When you clone a volume of a stopped container that container starts automatically. I think this may be dangerous without a warning and without allowing to avoid such start of the stopped container.

Add the steps to reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Describe the expected behavior A clear and concise description of what you expected to happen.

Optional: Add screenshots If applicable, add screenshots to help explain your problem.

Output of docker extension version:

(paste your output here)

Output of docker version:

(paste your output here)

Include extension console logs If relevant, you can add console logs that might include some trace related to the bug you're reporting

Additional context Add any other context about the problem here.

Describe the bug Sorting by size is not correct.

Add the steps to reproduce Steps to reproduce the behavior:

1. Go to the Volumes Backup & Share extension.
2. Click on the Size header column.
3. See the volumes are sorted incorrectly.

Describe the expected behavior The volumes should be sorted correctly depending on their size (including the unit, not just the numeric value).

Optional: Add screenshots

Output of docker extension version:

Client Version: v0.2.13
Server API Version: 0.3.0

Output of docker version:

(paste your output here)

Include extension console logs If relevant, you can add console logs that might include some trace related to the bug you're reporting

Additional context Add any other context about the problem here.

What does this PR do?

• Changes current notifications and uses Snackbars.
  • This gives us the ability of adding custom links the user can click after an action has finished.
  • Only created volumes and used images are displayed within Snackbars.

Notes for the reviewer

• Please review each action in case there is some link that is not working.

Screenshot

This PR:

• Adds support for more archive formats: zstd (.tar.zst) and bzip2 (.tar.bz2).
• The default archive format when exporting has changed from gzip (.tar.gz) to zstd (.tar.zst). Also, the compression implementation for gzip has changed to pigz (parallel implementation of gzip) which is faster.

I’ve run some benchmarks in GHA (2-cpu VM) with a volume that contains 4GB of Postgres data:

goos: linux
goarch: amd64
cpu: Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz

Regarding time:

name                                                                          time/op
ExportVolume/compression_docker.io/felipecruz/postgres_pgdata_4gb_.tar.gz-2    122s ± 0%
ExportVolume/compression_docker.io/felipecruz/postgres_pgdata_4gb_.tar.zst-2  46.9s ± 0%
ExportVolume/compression_docker.io/felipecruz/postgres_pgdata_4gb_.tar.bz2-2   429s ± 0%

Regarding compressed size:

2f91f352f0ba381893b9e15ea87db0e28a88aa6e28070c07892681d7a0d6ba6b.tar.gz - Size: 1690867939 bytes (1.69 GB)
2f91f352f0ba381893b9e15ea87db0e28a88aa6e28070c07892681d7a0d6ba6b.tar.zst - Size: 1593686093 bytes (1.59 GB)
2f91f352f0ba381893b9e15ea87db0e28a88aa6e28070c07892681d7a0d6ba6b.tar.bz2 - Size: 1328059635 bytes (1.32 GB)

Issue type: Unable to backup volume using extension “Volumes Backup & Share” OS Version / Build: Windows 11 Version 22H2 (Build: 22621.674) App version: v.4.13.1 Steps to reproduce: “Volumes Backup & Share” > “Export volume” > “To: Local File” > “.tar.zst” > “Directory” > “Select directory” > “” returns Failed to backup volume to C:\Users\Desktop: {“message”:“Internal Server Error”}. HTTP status code: 500

Diagnostic ID: 6FD65E53-DD8F-44DB-A774-357A2EE71651/20221102203305

Hello,

Trying to export a volume using the Docker extension “Volumes Backup & Share” but it fails regardless of destination: C: C:\Users\Desktop D:
^ External USB with the error: Failed to backup volume to C:\Users\Desktop: {“message”:“Internal Server Error”}. HTTP status code: 500

The container the volume belongs to isn’t started.

Would appreciate any and all help!

Best Regards - TheSwede86

Currently, the reason why the list of volumes takes some time to load is that calculating the size of each is an expensive operation (the bigger the volumes, the longer it'll take) and it retrieves the list of containers for every volume.

Instead, we could:

1. Retrieve the list of volumes (without calculating their size). This should be much faster.
2. Once the list is loaded, calculate the volume size and the containers attached in the background.

https://user-images.githubusercontent.com/15997951/189663566-c250a836-cc0e-4c96-ae22-c53c1b600974.mov

Context: https://github.com/docker/volumes-backup-extension/issues/94#issuecomment-1286765934

Given the REACT_APP_MUI_LICENSE_KEY is not shared in the repo, we should not make the docker build operation fail if it's not present:

Before

$ make build-extension

docker buildx build \
		--secret id=BUGSNAG_API_KEY \
		--secret id=REACT_APP_MUI_LICENSE_KEY \
		--build-arg BUGSNAG_RELEASE_STAGE=local \
		--build-arg BUGSNAG_APP_VERSION=latest \
		--load \
		--tag=docker/volumes-backup-extension:latest \
		.
ERROR: failed to stat REACT_APP_MUI_LICENSE_KEY: stat REACT_APP_MUI_LICENSE_KEY: no such file or directory
make: *** [build-extension] Error 1

This pull request re-pins the Docker base image busybox:1.35.0 in Dockerfile to the current digest.

https://github.com/docker/volumes-backup-extension/blob/9ba92c8921132249edbd61aa662dcf02286a6f41/Dockerfile#L48-L48

Digest sha256:d7f4aada301c0f13d93ceed62fef318c195c38bf430fc8bfbdf1d850514422ff references a multi-CPU architecture image manifest. This image supports the following architectures:

• sha256:f1d6d77ed9ca269e850013ce6d5d73aef0c737d291bbc573e6da6245c49d62ea linux/ppc64le

Update busybox

Changes:

- https://github.com/docker-library/busybox/commit/b8bb85f: Merge pull request https://github.com/docker-library/busybox/pull/146 from infosiftr/buildroot-2022.08.1
- https://github.com/docker-library/busybox/commit/b7a7954: Update buildroot to 2022.08.1

-/bin/sh -c #(nop) ADD file:eb6acc9b156cd0a00e3bd36aa2a6a5804c67949324d220c6ad53ac98af9be836 in /
+/bin/sh -c #(nop) ADD file:83c5003206e1b283bbf673e0e1806cc7010d6ea90659bbd75b55d51395f191c0 in /
 /bin/sh -c #(nop)  CMD ["sh"]

Pinning FROM lines to digests makes your builds repeatable. Atomist will raise new pull requests whenever the tag moves, so that you know when the base image has been updated. You can follow a new tag at any time. Just replace the digest with the new tag you want to follow. Atomist, will switch to following this new tag.

File changed:

• Dockerfile

This pull request pins the Docker base image alpine:3.16.2 in docker/images/alpine-tar-zstd/Dockerfile to the current digest.

https://github.com/docker/volumes-backup-extension/blob/fd8944ab457731bc8d556fa1ac5a63382ad9dd78/docker/images/alpine-tar-zstd/Dockerfile#L1-L1

Digest sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad references a multi-CPU architecture image manifest. This image supports the following architectures:

• sha256:1d96e60e5270815238e999aed0ae61d22ac6f5e5f976054b24796d0e0158b39c linux/386
• sha256:1304f174557314a7ed9eddb4eab12fed12cb0cd9809e4c28f29af86979a3c870 linux/amd64
• sha256:5da989a9a3a08357bc7c00bd46c3ed782e1aeefc833e0049e6834ec1dcad8a42 linux/arm/v6
• sha256:0c673ee68853a04014c0c623ba5ee21ee700e1d71f7ac1160ddb2e31c6fdbb18 linux/arm/v7
• sha256:ed73e2bee79b3428995b16fce4221fc715a849152f364929cdccdc83db5f3d5c linux/arm64/v8
• sha256:fa30af02cc8c339dd7ffecb0703cd4a3db175e56875c413464c5ba46821253a8 linux/ppc64le
• sha256:c2046a6c3d2db4f75bfb8062607cc8ff47896f2d683b7f18fe6b6cf368af3c60 linux/s390x

Pinning FROM lines to digests makes your builds repeatable. Atomist will raise new pull requests whenever the tag moves, so that you know when the base image has been updated. You can follow a new tag at any time. Just replace the digest with the new tag you want to follow. Atomist, will switch to following this new tag.

File changed:

• docker/images/alpine-tar-zstd/Dockerfile

This pull request pins the following Docker base images in Dockerfile to their current digests.

https://github.com/docker/volumes-backup-extension/blob/09c9759c192768acab777d4f8a0362ab611f18fd/Dockerfile#L1-L1

https://github.com/docker/volumes-backup-extension/blob/09c9759c192768acab777d4f8a0362ab611f18fd/Dockerfile#L13-L13

https://github.com/docker/volumes-backup-extension/blob/09c9759c192768acab777d4f8a0362ab611f18fd/Dockerfile#L27-L27

Digest sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad references a multi-CPU architecture image manifest. This image supports the following architectures:

• sha256:1d96e60e5270815238e999aed0ae61d22ac6f5e5f976054b24796d0e0158b39c linux/386
• sha256:1304f174557314a7ed9eddb4eab12fed12cb0cd9809e4c28f29af86979a3c870 linux/amd64
• sha256:5da989a9a3a08357bc7c00bd46c3ed782e1aeefc833e0049e6834ec1dcad8a42 linux/arm/v6
• sha256:0c673ee68853a04014c0c623ba5ee21ee700e1d71f7ac1160ddb2e31c6fdbb18 linux/arm/v7
• sha256:ed73e2bee79b3428995b16fce4221fc715a849152f364929cdccdc83db5f3d5c linux/arm64/v8
• sha256:fa30af02cc8c339dd7ffecb0703cd4a3db175e56875c413464c5ba46821253a8 linux/ppc64le
• sha256:c2046a6c3d2db4f75bfb8062607cc8ff47896f2d683b7f18fe6b6cf368af3c60 linux/s390x

https://github.com/docker/volumes-backup-extension/blob/09c9759c192768acab777d4f8a0362ab611f18fd/Dockerfile#L36-L36

https://github.com/docker/volumes-backup-extension/blob/09c9759c192768acab777d4f8a0362ab611f18fd/Dockerfile#L45-L45

Digest sha256:b8f68c62fe862281bf598060f15cb080ef778dc9db19f136d19a3531ffcb9aa0 references a multi-CPU architecture image manifest. This image supports the following architectures:

• sha256:fa6edea1c6be8ee2248a3a5c6fba82821a3f0eab14a1d344a7a5f497a9d010df linux/386
• sha256:b7362a56f02a9312093492d1a02fabd807b4830c393211d93f22de89f1f845da linux/amd64
• sha256:383c6eb6d701ba4cf3fe031ef98c9464bf7a5daea89ec53d939b8038c58acff7 linux/arm/v5
• sha256:2d57ea9062df274ff468746768c973a2604e85eea6f8c51b28ba37aa29bfc3a9 linux/arm/v6
• sha256:40894c51dcd24812e4ecc9b0ec87e97e75d7d2f388687325f0a0f01e9d35fd78 linux/arm/v7
• sha256:90ee8d93c0261e5299d2076231fec99c8f5cb381199195b3442e7da78de84332 linux/arm64/v8
• sha256:3e090f14513cc4ca2958f6ba7747c39c168b84c333cac1c9c3c6d35eeee85a70 linux/mips64le
• sha256:ccc340b07786525604d95e1a7b5155ec4b190a592747981ac20fcd5948df5f82 linux/ppc64le
• sha256:cba3c501d7a29136ec9bf8cc555bdc6f1cbd52b6e8f49b5cc89244fb5fad775b linux/riscv64
• sha256:722fa10feaf0c9bfd06c8b0d4e53db3c1890dd927315ac4851fe95b42cc15a9f linux/s390x

Pinning FROM lines to digests makes your builds repeatable. Atomist will raise new pull requests whenever the tag moves, so that you know when the base image has been updated. You can follow a new tag at any time. Just replace the digest with the new tag you want to follow. Atomist, will switch to following this new tag.

File changed:

• Dockerfile

What does this PR do?

• Updates the Export dialog to include the push to registry option.
• Cleanup actions - remove unused.

| Updated dialog | Cleanup actions | | --- | --- | | | |

Is your feature request related to a problem? Please describe. Schedule a backup, say every day or week.

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe. TBD

Describe the solution you'd like Currently, Docker extension assigns random volume names when importing folders to avoid naming conflicts and gives the option to name before importing. Is it possible to add an additional option beside those to name imported volumes/images by folder names as well.

Describe alternatives you've considered N/A

Additional context Related to this reddit thread - https://www.reddit.com/r/docker/comments/x11m4n/comment/iq8x2bn/?utm_source=share&utm_medium=web2x&context=3

Is your feature request related to a problem? Please describe. Backup all volumes that belong to an entire stack

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe. I compressed a folder from Mac Os Finder which creates a zip file. But I couldn't import it and had to manually create a gzip file. However, the extension was .tgz instead of .tar.gz.

Describe the solution you'd like I wish I can import

• zip files
• gzip files with any extension

Is your feature request related to a problem? Please describe. I was importing a tar.gz and I mechanically dragged it over Docker Desktop (the extension being open) and realise that it is not possible

Describe the solution you'd like When dropping a file on the app I wish the import dialog opens

Describe alternatives you've considered none, just click on the button and navigate to the folder where my tar.gs is.

Additional context Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.

No

Describe the solution you'd like

I would <3 a cli for this when I install the extension

Describe alternatives you've considered

Using the UI, but sometimes I prefer the terminal

Additional context