Mount command has disappeared

[nickchomey]

I just tried to use mount, but it doesnt exist. I dont see anything in the changelogs to suggest that it was removed, and the docs still have rustic mount

Have I done something wrong?

[kapitainsky]

I dont see anything in the changelogs to suggest that it was removed,

And I do not see anything in the changelogs to suggest that it was ever added:)

Use rustic webdav instead. Then mount it.

Or maybe try TUI rustic snapshots -i. Since its introduction I use it exclusively instead of mounting.

[nickchomey]

I'm almost certain that mount existed at some point. And, again, its in the docs...

rustic snapshots -i do seem to do anything for me.

[kapitainsky]

I'm almost certain that mount existed at some point. And, again, its in the docs...

I am not 100% sure here myself. But docs can be misleading as some parts are just copied from restic and not updated.

rustic snapshots -i do seem to do anything for me.

It starts very nice TUI. make sure you provided your repo details. Either via toml or directly in the command line. Also wait a moment - it takes few moments to read all it needs.

[aawsome]

HI @nickchomey!

About the mount command: Yes, mount has been introduced a while ago. However, it needs support from the OS and additional dependencies (installed libraries) in order to build. Therefore it is only supported for linux currently and is gated behind the mount feature flag. How did you get your rustic binary? The linux versions build via github should contain the mount command, but you may have it installed via you package manager which uses its own build setup, see also #1584.

The alternatives (webdav or interactive mode) proposed by @kapitainsky build and work in any setup; they are compiled-in by default and would need opt-out when compiling.

I'll turn this into a discussion as it might be also interesting for others.

[nickchomey]

Though, now i'm not seeing mount when gnu is installed via cargo binstall. very weird - it worked earlier.

I'm just going to use the github backend - its what i've largely defaulted to in general, and it works for rustic.

[aawsome]

@nickchomey If you install rustic by any tool/utiil which self-compiles rustic in one or the other way, the feature mount (and installed fuse libraries) must be used when compiling. Setting this feature can be only done by that tool or by yourself - depending on how the tool works.
If you self-compile, use cargo build --features mount.
Note that many utils use stored and pre-compiled binaries - for those it depends how the compilation was called. The binary in the github release should contain the mount feature.

About musl: This is only related to the used libc. With musl, libc is statically compiled into the binary whereas with gnu the gnu libc is used as a shared library. This is completely independent from the mount feature - if you compile the musl target with that feature, you'll get the mount command. The musl target is typically chosen to get a dependency-free binary (not depending on any shared library) and a binary compiled with the mount feature will always depend on some libfuse shared library - so I think that often the musl target will be compiled without mount. IIRC this is also what we do on the github builds.

[nickchomey]

In all cases (except perhaps for cargo-binstall) it was downloading from rustic Github releases. I just manually downloaded the x86-64 Linux musl and it does not have mount aavai) available. Something is wrong with your Github builds

[aawsome]

Hey @nickchomey, there is nothing wrong with the github builds. As I said, we intentionally do not compile with the mount feature for the musl target - we also never claimed (or documented) anywhere in which builds we add which feature.

I added a disclaimer in the mount docu which hopefully makes things a bit more clear, see https://rustic.cli.rs/docs/commands/restore/using_mount.html.

[nickchomey]

Oh, sorry, I misread what you had said. Understood - musl doesn't have mount, and gnu does. But only on Linux. It might be worth mentioning that in the docs.