ericreager

Thank you for responding. I'd started to go down this road but it's which arguments are "relevant to the pg-upgrade container" I get stuck on. Here is what my docker run command looks like for the existing baserow container with some redactions: docker run -d --name='baserow' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="**********" -e HOST_CONTAINERNAME="baserow" -e 'BASEROW_PUBLIC_URL'='http://*************' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:80]' -l net.unraid.docker.icon='https://gitlab.com/baserow/baserow/-/raw/develop/deploy/cloudron/logo.png' -p '****:80/tcp' -v '/mnt/user/appdata/baserow':'/baserow/data':'rw' 'baserow/baserow' ********************************************** Are you able to tell me which of the lines above should get inserted into the pg-upgrade run command?

Hello - would anyone be able provide the steps for upgrading the data directory to be compatible with PostgreSQL 15, specific for this container on Unraid? I'm not exactly sure how to adapt the instructions from the Baserow site and I'm pretty paranoid about messing this DB up. EDIT: I guess to clarify the part I'm shaky on, according to Baserow's instructions, I should stop the container, backup the instance, then run this in the Unraid console: docker run \ --name baserow-pgautoupgrade \ # ALL THE ARGUMENTS YOU NORMALLY ADD TO YOUR BASEROW INSTANCE --restart no \ baserow/baserow-pgautoupgrade:1.24.2 I'm not sure exactly what I'm supposed to put in the # ALL THE ARGUMENTS YOU NORMALLY ADD TO YOUR BASEROW INSTANCE part.

Figured it out partially on my own. The order set on the Docker tab seems to be stored in /boot/config/plugins/dockerMan/userprefs.cfg, each line having a container name in quotes. The script below goes through the config line by line and does a docker start on whatever is contained within the quotes, with a 30 second wait between each container. Ideally it should only wait the amount of time set for each container on the Docker tab, but I haven't found where those values are stored yet. #!/bin/bash # Specify the path to your .cfg file CFG_FILE="/boot/config/plugins/dockerMan/userprefs.cfg" # Check if the file exists if [ ! -f "$CFG_FILE" ]; then echo "Error: Config file not found." exit 1 fi # Read the .cfg file line by line and start Docker containers while IFS= read -r line do # Extract container name within quotes container_name=$(echo "$line" | sed -n 's/.*"\(.*\)".*/\1/p') # Start Docker container docker start "$container_name" # Check the exit status if [ $? -eq 0 ]; then echo "Container '$container_name' started successfully. Waiting to start next Container." sleep 30 # Wait for 30 seconds before starting the next container else echo "Error: Failed to start container '$container_name'." fi done < "$CFG_FILE" echo "All containers started."

Hi All - I'm working on a script that involves stopping and then starting all docker containers. I have it working, but the containers start in some default order and not the top-down order I have them set in the Docker tab. Is there a way to have them start according to the order and delay settings in the Docker tab? Or does the script just need to start them individually in the desired order? Thanks in advance, Eric

I'll just add a "me too" for having LAN_NETWORK incorrectly configured, worked fine for last few months, lost WebUI sometime in the last couple days, corrected LAN_NETWORK, now everything is working again. I also have not made any changes to my network and I checked my router's update log and nothing updated since 9/9. And thanks to all who worked that out.

That did the trick, licenses are all squared away and all disks back in operation as expected. Thank you!

forgive the question as I'm not familiar with the command: Will this have any destructive impact on the contents of the disk or its relationship to the array? Or after rebooting will whatever disk I chose return to the state it was in when the array was stopped? Like if I choose my parity disk, am I going to end up having to rebuild the parity?

Thanks, the 7 attached disks are all assigned array/pool devices. I could probably remove one of them temporarily, but I'd rather not if it can be avoided. I've already submitted the support contact form, I will wait and see what they say. Thanks again.

Same result. Even with the array stopped, it still recognizes that my GUID is associated with 7 attached devices.

I have not, I will try that now.

I purchased the Basic license using the summer promo code with the intent of then purchasing the Basic > Pro upgrade also using the promo. However when I try to activate the Basic license it says it can't because I have too many attached disks (7) and doesn't give me any direct patch to purchase an upgrade. Do I have any options to upgrade the Basic license to the Pro license using the promo here? Right now it seem like I have to purchase either the Plus or Pro at full price and eat what I already spent on the Basic.