sshfs on proxmox VE8

[rubenzsolt]

I've installed sshfs package and it installed fuse3 but it removed the fuse package, any problem is possible from this?

dpkg: fuse: dependency problems, but removing anyway as you requested:
pve-cluster depends on fuse.

# apt-get -y install sshfs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  fuse3
The following packages will be REMOVED:
  fuse
The following NEW packages will be installed:
  fuse3 sshfs
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Need to get 81.6 kB of archives.
After this operation, 94.2 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main amd64 fuse3 amd64 3.14.0-4 [35.9 kB]
Get:2 http://deb.debian.org/debian bookworm/main amd64 sshfs amd64 3.7.3-1.1 [45.6 kB]
Fetched 81.6 kB in 0s (295 kB/s)
dpkg: fuse: dependency problems, but removing anyway as you requested:
 pve-cluster depends on fuse.

(Reading database ... 47071 files and directories currently installed.)
Removing fuse (2.9.9-6+b1) ...
update-initramfs: deferring update (trigger activated)
Selecting previously unselected package fuse3.
(Reading database ... 47060 files and directories currently installed.)
Preparing to unpack .../fuse3_3.14.0-4_amd64.deb ...
Unpacking fuse3 (3.14.0-4) ...
Selecting previously unselected package sshfs.
Preparing to unpack .../sshfs_3.7.3-1.1_amd64.deb ...
Unpacking sshfs (3.7.3-1.1) ...
Setting up fuse3 (3.14.0-4) ...
Installing new version of config file /etc/fuse.conf ...
update-initramfs: deferring update (trigger activated)
Setting up sshfs (3.7.3-1.1) ...

 

[t.lamprecht]

I've installed sshfs package and it installed fuse3 but it removed the fuse package, any problem is possible from this?

In this specific case, no, as fuse3 has a versioned Provides and Replaces entries in its package dependency specification for fuse, see apt show fuse3 So, it can replace fuse as long as a package doesn't depend on a too old version.
As pve-cluster doesn't depend on a specific version this is fine, the lower level dpkg tool doesn't have the full dependency information available, so it spits out a warning that something might be at odd, but the higher-level apt tool "sees" the whole picture here and can know that this is fine due the newly added package being a replacement for the older one, that's why pve-cluster is not tried to be removed (we'd also have safeguards in place against removing key Proxmox VE packages).

PS. I'd recommend against blindly passing the -y flag. apt will show you what will happen, i.e., what packages will be installed and which will be removed, if any, upfront if you omit that -y flag and ask you for confirmation. This is always safer and gives you more information upfront.

 

[PaulVM]

Calirification: this answer is valido also for ceph-fuse?

dpkg: fuse: dependency problems, but removing anyway as you requested :pve-cluster depends on fuse. ceph-fuse depends on fuse.

And, curiosity: I am not a developer, so my knowledge is limited, but first curiosity that come to me is: why still use the old fuse version in the new Proxmox, if it can use the new?
Thanks, P.

 

[mathx]

bump. This question was not answered. Seems key since many utilities are using fuse3 and dont want to pull the fuse package rug out from under pve-cluster et al.

 

[t.lamprecht]

The original question was answered, so you probably mean the ceph-fuse one. As long as you got the correct repos configured for the upgrade (i.e., also changed the ones from ceph to match the distro), then this is fine; but without taking a close look on what you did I naturally cannot guarantee that – but if you follow the upgrade how closely and running the pve7to8 checker script doesn't produce any error or warning it's likely that you're fine.

 

[mathx]

Aha rereading your answer it seems you did answer, apologies, but it wasnt immediately clear.

"As pve-cluster doesn't depend on a specific version this is fine" was the key part.