starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Urbackup Server LXC - Option fuse is required for mounting image backups #429

New Issue
Closed
opened 2026-02-04 18:50:15 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 18:50:15 +03:00
Owner
Copy Link

Originally created by @B0F1B0 on GitHub (Feb 2, 2025).

Originally assigned to: @michelroegl-brunner on GitHub.

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

UrBackup Server LXC

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/urbackupserver.sh)"

📝 Provide a clear and concise description of the issue.

The Urbackup LXC container requires the Option: "fuse" so that you can mount Image Backups via the GUI.
Without the Option: "fuse" no Image Backups can be mounted.

Image

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. Create the Urbackup Server LXC on Proxmox shell with
    bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/urbackupserver.sh)"

  2. Install the Urbackup-Client on Windows

  3. Create a Image backup

  4. Go to Images backups in the GUI - Select the Volume C: from the client -

  5. Press: Mount image

Image

❌ Paste the full error output (if available).

cat /var/log/urbackup-fuse.log

2025-02-02 12:35:58: Mounting VHD via fuse...
2025-02-02 12:35:58: Volume offset is 524288 bytes. Configure via --offset
2025-02-02 12:35:58: ERROR: Error mounting fuse filesystem

🖼️ Additional context (optional).

With the Option: fuse, you can mount the Volume C: from the Client via GUI.

Image

Originally created by @B0F1B0 on GitHub (Feb 2, 2025). Originally assigned to: @michelroegl-brunner on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? UrBackup Server LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/urbackupserver.sh)" ### 📝 Provide a clear and concise description of the issue. The Urbackup LXC container requires the Option: "**fuse**" so that you can mount **Image Backups** via the GUI. Without the Option: "**fuse**" no Image Backups can be mounted. ![Image](https://github.com/user-attachments/assets/faca4aff-2f53-40d3-ae28-a337e625adda) ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. Create the Urbackup Server LXC on Proxmox shell with `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/urbackupserver.sh)"` 2. Install the Urbackup-Client on Windows 3. Create a Image backup 4. Go to Images backups in the GUI - Select the Volume C: from the client - 5. Press: `Mount image` ![Image](https://github.com/user-attachments/assets/0b4c41ef-d99a-4c16-a18c-71b0c3c0f9f7) ### ❌ Paste the full error output (if available). `cat /var/log/urbackup-fuse.log` 2025-02-02 12:35:58: Mounting VHD via fuse... 2025-02-02 12:35:58: Volume offset is 524288 bytes. Configure via --offset 2025-02-02 12:35:58: ERROR: Error mounting fuse filesystem ### 🖼️ Additional context (optional). With the Option: `fuse`, you can mount the Volume C: from the Client via GUI. ![Image](https://github.com/user-attachments/assets/103800db-27bb-4f7d-9234-abc022cb7a29)
OVERLORD commented 2026-02-04 18:50:23 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 3, 2025):

I haven't seen the option to set container features during the execution of LXC creation script, maybe i'm just blind.
Talked to @michelroegl-brunner about it, we might be able to do it in the future, just need him to check the sources.

Stay tuned.

In the time being, we could add a note to the website which would instruct users to manually check the FUSE feature in the LXC options

@tremor021 commented on GitHub (Feb 3, 2025): I haven't seen the option to set container features during the execution of LXC creation script, maybe i'm just blind. Talked to @michelroegl-brunner about it, we might be able to do it in the future, just need him to check the sources. Stay tuned. In the time being, we could add a note to the website which would instruct users to manually check the FUSE feature in the LXC options
OVERLORD commented 2026-02-04 18:50:27 +03:00
Author
Owner
Copy Link

@B0F1B0 commented on GitHub (Feb 3, 2025):

It could be done in the urbackupserver install script with:

pct set $CTID -features fuse=1,nesting=1
pct reboot $CTID

@kris701
for example like this:

#!/usr/bin/env bash
source <(curl -s https://raw.githubusercontent.com/community-scripts/ProxmoxVE/refs/heads/main/misc/build.func)
# Copyright (c) 2021-2025 community-scripts ORG
# Author: Kristian Skov
# License: MIT | https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE
# Source: https://www.urbackup.org/

# App Default Values
APP="UrBackup Server"
var_tags="web"
var_cpu="1"
var_ram="1024"
var_disk="16"
var_os="debian"
var_version="12"
var_unprivileged="0"

# App Output & Base Settings
header_info "$APP"
base_settings

# Core
variables
color
catch_errors

function update_script() {
    header_info
    check_container_storage
    check_container_resources
    if [[ ! -d /var/urbackup ]]; then
        msg_error "No ${APP} Installation Found!"
        exit
    fi
    msg_info "Updating ${APP} LXC"
    apt-get update &>/dev/null
    apt-get -y upgrade &>/dev/null
    msg_ok "Updated Successfully"
    exit
}

start
build_container

# enable FUSE
pct set $CTID -features fuse=1,nesting=1

description

msg_ok "Completed Successfully!\n"
echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}"
echo -e "${INFO}${YW} Access it using the following IP:${CL}"
echo -e "${TAB}${GATEWAY}${BGN}${IP}:55414${CL}"

# restart container to activate FUSE
pct reboot $CTID
@B0F1B0 commented on GitHub (Feb 3, 2025): It could be done in the urbackupserver install [script](https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/urbackupserver.sh) with: `pct set $CTID -features fuse=1,nesting=1` `pct reboot $CTID` @kris701 for example like this: ```bash #!/usr/bin/env bash source <(curl -s https://raw.githubusercontent.com/community-scripts/ProxmoxVE/refs/heads/main/misc/build.func) # Copyright (c) 2021-2025 community-scripts ORG # Author: Kristian Skov # License: MIT | https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE # Source: https://www.urbackup.org/ # App Default Values APP="UrBackup Server" var_tags="web" var_cpu="1" var_ram="1024" var_disk="16" var_os="debian" var_version="12" var_unprivileged="0" # App Output & Base Settings header_info "$APP" base_settings # Core variables color catch_errors function update_script() { header_info check_container_storage check_container_resources if [[ ! -d /var/urbackup ]]; then msg_error "No ${APP} Installation Found!" exit fi msg_info "Updating ${APP} LXC" apt-get update &>/dev/null apt-get -y upgrade &>/dev/null msg_ok "Updated Successfully" exit } start build_container # enable FUSE pct set $CTID -features fuse=1,nesting=1 description msg_ok "Completed Successfully!\n" echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}" echo -e "${INFO}${YW} Access it using the following IP:${CL}" echo -e "${TAB}${GATEWAY}${BGN}${IP}:55414${CL}" # restart container to activate FUSE pct reboot $CTID ```
OVERLORD commented 2026-02-04 18:50:40 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Feb 3, 2025):

Merged.

@michelroegl-brunner commented on GitHub (Feb 3, 2025): Merged.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#429
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?