No valid storage found for 'rootdir' (Container).

[memilanuk]

I hit a bit of a snag here... for some reason, when I try to use LXC install scripts from the new repo (here), I get the following error:

       __     ____      _____     
      / /__  / / /_  __/ __(_)___ 
 __  / / _ \/ / / / / / /_/ / __ \
/ /_/ /  __/ / / /_/ / __/ / / / /
\____/\___/_/_/\__, /_/ /_/_/ /_/ 
              /____/              
  ⚙️  Using Default Settings on node pve1
  🆔  Container ID: 103
  🖥️  Operating System: ubuntu (24.04)
  📦  Container Type: Unprivileged
  💾  Disk Size: 8 GB
  🧠  CPU Cores: 2
  🛠️  RAM Size: 2048 MiB
  🚀  Creating a Jellyfin LXC using the above default settings
  
   ✖️   No valid storage found for 'rootdir' (Container).

[ERROR] in line 1094: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?

root@pve1:~# 

Same for pi-hole, and postgresql.

Meanwhile, I seem to have no problem with clicking the "Create CT" button and creating a vanilla Ubuntu or Debian LXC using downloaded container images. So... yes, I do have valid storage for containers.

Any ideas?

[MickLesk]

rootdir is the container storage, if this not exist, our scripts doesnt work.

pvesm status -content rootdir

[memilanuk]

Well, there is container storage, or else I wouldn't be able to run or install any of the ones I have, right?

root@pve1:~# pvesm status -content rootdir
Name           Type     Status           Total            Used       Available        %
storage     lvmthin     active       957095936        25554461       931541474    2.67%
root@pve1:~# 

[memilanuk]

@MickLesk is the script looking for something specific, like 'local-lvm', or something else?

[MickLesk]

No Just Proxmox internal commands

[memilanuk]

So... I wonder why it's returning an error, when there clearly is a 'rootdir' returned by the 'pvesm' command?🤔

[MickLesk]

Just an simple bash call

function check_storage_support() {
  local CONTENT="$1"
  local -a VALID_STORAGES=()

  while IFS= read -r line; do
    local STORAGE=$(awk '{print $1}' <<<"$line")
    [[ "$STORAGE" == "storage" || -z "$STORAGE" ]] && continue
    VALID_STORAGES+=("$STORAGE")
  done < <(pvesm status -content "$CONTENT" 2>/dev/null | awk 'NR>1')

  [[ ${#VALID_STORAGES[@]} -gt 0 ]]
}

# This checks for the presence of valid Container Storage and Template Storage locations
msg_info "Validating Storage"
if ! check_storage_support "rootdir"; then

  msg_error "No valid storage found for 'rootdir' (Container)."
  exit 1
fi

[memilanuk]

Well... my shell scripting foo is pretty weak, almost to the point of non-existent, but if I'm reading the line that calls pvesm with "rootdir" as it's argument correctly... when I call that command by itself from the root prompt I get the following:

root@pve1:~# pvesm status -content rootdir  2>/dev/null | awk 'NR>1'
storage     lvmthin     active       957095936        27181524       929914411    2.84%
root@pve1:~# 

I'm guessing the script is comparing that value against VALID_STORAGES, but I have no real idea of how it's driving/populating that value?