sshfs on proxmox VE8

rubenzsolt

Member
Nov 13, 2020
6
0
6
44
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.

Code:
# 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) ...
 
Last edited:
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 has 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.
 
  • Like
Reactions: Phyrene
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.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!