Minarca 7.1.0 Released!

We’re happy to announce that Minarca Server and Minarca Client version 7.1.0 are now available! :sparkles:

Here’s what’s new:


Minarca Server 7.1.0

Added

  • Added a helpful tooltip for repo notes on the user edit page in the admin interface.
  • New --test-config command line option to validate your configuration file syntax before applying it.

Fixed

  • Fixed mount/unmount ordering issue in jailed repositories.
  • Various CI and packaging fixes for Docker image builds and Debian packages.

Changed

  • Improved status badge styling for active and deleted entries for better visual clarity.
  • Refactored disk usage aggregation for improved performance and maintainability.

Removed

  • Cleaned up redundant template attributes and obsolete files from the codebase.

Misc

  • Updated French translations.

Minarca Client 7.1.0

Added

  • Network drive support on Windows: Automatic remount of network drives when backing up.
  • New prompt dialog to help configure network locations directly from the UI.
  • Added support for UNC paths on Windows, making it easier to back up files stored on network shares.

Fixed

  • Fixed the macOS bundle executable name issue in Info.plist.
  • Resolved several static analysis warnings for improved code quality and stability.

Misc

  • Improved performance with async file I/O for SSH key exchange and log writes.
  • Backup process now continues across anchors even if one fails, improving overall backup resilience.
  • Updated French translations.
  • Various internal refactoring for better maintainability.

Thanks to everyone in the community for your continued support and feedback!

If you run into any issues after upgrading, please don’t hesitate to reach out here or open a ticket on our GitLab.

Happy backing up!

1 Like

Hi! When will the docker server version for 7.1 be available?

Hello Wanni,

Thanks for using the new discourse !

When will the docker server version for 7.1 be available?

The docker image is already release. Usually, everything get release automatically: deb, tar.gz and docker image.

docker pull ikus060/minarca-server:7.1.0

What make you believe it was not out yet ?

I’m using “ikus060/minarca-server:latest” as image source which pulls 6.2.5. So it seems I have to use always a specific version to update it to latest one.

Hum, indeed.

New releases doesn’t upgrade the latest tag. I think I should event delete this tag completely. It’s not a good practice to use the latest tag anyway for any docker image.

I will take a look at it and come back to you.

Why is it not a good practice to use “latest”? I’m using portainer to manage all my containers (or better “stacks” - means docker compose). As such portainer shows you all stacks/containers where a new image is available so you don’t have to follow different websites to find out if an update is available. And then you can still decide if you want to update or not.

@Wanni48 You can search online about good or bad pratice related to latest: https://medium.com/@robertdiebels/are-you-using-the-latest-tag-well-stop-it-6d6390f9623a

latest tag has been delete. If you want a tag to keep track of the version you may use “7” to target any 7.x.x version for the near future.