Azuracast Install on Rockstor built on openSUSE NAS

Azuracast Install on Rockstor built on openSUSE NAS

I have a Rockstor built on openSUSE NAS. It has Portainer. Can I install Azuracast on it? Here are the specs:

ip = 192.168.1.101: Rockstor-101:~ # free

total used free shared buff/cache available

Mem: 7890512 915280 6274612 27032 980824 6975232

Swap: 2097148 0 2097148

Rockstor-101:~ # df -h

Filesystem Size Used Avail Use% Mounted on

/dev/sdd4 58G 6.4G 49G 12% /

devtmpfs 4.0M 8.0K 4.0M 1% /dev

tmpfs 3.8G 16K 3.8G 1% /dev/shm

efivarfs 16E 0 -5.1K 0% /sys/firmware/efi/efivars

tmpfs 1.6G 9.3M 1.5G 1% /run

tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysctl.service

tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service

tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service

/dev/sdd4 58G 6.4G 49G 12% /.snapshots

/dev/sdd4 58G 6.4G 49G 12% /boot/grub2/i386-pc

/dev/sdd4 58G 6.4G 49G 12% /srv

/dev/sdd4 58G 6.4G 49G 12% /root

/dev/sdd4 58G 6.4G 49G 12% /home

/dev/sdd4 58G 6.4G 49G 12% /boot/grub2/x86_64-efi

/dev/sdd4 58G 6.4G 49G 12% /usr/local

/dev/sdd4 58G 6.4G 49G 12% /var

tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-vconsole-setup.service

/dev/sdd4 58G 6.4G 49G 12% /tmp

/dev/sdd2 64M 2.4M 62M 4% /boot/efi

/dev/sdd4 58G 6.4G 49G 12% /opt

tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup.service

overlay 58G 6.4G 49G 12% /var/lib/docker/overlay2/e6c192366cc010711625fcf98a77c1d2aba1cf729a5efdcd736ac630e63b6603/merged

overlay 58G 6.4G 49G 12% /var/lib/docker/overlay2/55016e3a8245b6b5e05cba353d36882b40953ca4e57c00c09039b68eb6eefd4e/merged

overlay 58G 6.4G 49G 12% /var/lib/docker/overlay2/7242c3e7d2c8eb78b66a4bdd14bec00852f827b98b5b69d0c215b97471c02f6e/merged

tmpfs 3.8G 0 3.8G 0% /var/lib/docker/containers/4654748c0ff37ff6d1817594dde1455c4591b83c8f4c486663dd4c83978b8f43/mounts/secrets

tmpfs 3.8G 0 3.8G 0% /var/lib/docker/containers/76cbb6e29f9f4dc0df136c949eaaabf224cbb9c2f40d31021fd8b56404c58da7/mounts/secrets

tmpfs 3.8G 0 3.8G 0% /var/lib/docker/containers/5b79cefd8481c31b769e9b402429b714a88c7427699fca1a88196584aaabf45a/mounts/secrets

tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service

/dev/sda 954G 907G 48G 96% /mnt2/ssd_pool

/dev/mmcblk0p1 7.3G 5.9M 6.8G 1% /mnt2/MMC

/dev/sdb 19T 11T 8.1T 56% /mnt2/raid0_pool

/dev/sdd4 58G 6.4G 49G 12% /mnt2/ROOT

/dev/sda 954G 907G 48G 96% /mnt2/SSD_Scratch

/dev/mmcblk0p1 7.3G 5.9M 6.8G 1% /mnt2/mmc-8GTF4R

/dev/sdb 19T 11T 8.1T 56% /mnt2/share_raid0_pool

tmpfs 771M 12K 771M 1% /run/user/0

Rockstor-101:~ #

Gemini

Yes, you can run AzuraCast on your Rockstor NAS. Your system hardware easily clears AzuraCast's recommended requirements (2 GB RAM minimum, 20 GB disk space):

  • RAM: 8 GB total (~6.3 GB free / 6.9 GB available), which is plenty to handle the web interface, Icecast/Shoutcast, and Liquidsoap audio processing.
  • Storage: 49 GB free on your OS root drive (/), plus 8.1 TB free on your primary RAID pool (/mnt2/raid0_pool), giving you more than enough room for system files and media storage.

Step-by-Step Deployment via Portainer

Since Rockstor manages storage through Btrfs pools and shares, deploying AzuraCast as a Docker Stack in Portainer is the cleanest approach.

1

In the Rockstor Web UI, go to Storage → Shares and create a dedicated share (e.g., azuracast_data) on your pool. This ensures your persistent audio tracks and databases are safely mapped outside container filesystems.

2

Open Portainer Stacks

1 min

Log into Portainer (typically at [http://192.168.1.101:9000](http://192.168.1.101:9000)), select your primary environment (Local), go to Stacks in the left menu, and click + Add stack.

3

Paste Docker Compose Configuration

2 min

Name the stack azuracast and paste the standard single-instance Docker Compose layout into the web editor:

version: '3.8'

services:
  web:
    image: ghcr.io/azuracast/azuracast:latest
    container_name: azuracast
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
      - "8000:8000"
      - "8005:8005"
      - "8010:8010"
      - "8020:8020"
      - "8030:8030"
      - "8040:8040"
      - "8050:8050"
      - "8060:8060"
      - "8070:8070"
      - "8090:8090"
    volumes:
      - /mnt2/raid0_pool/azuracast_data:/var/azuracast/storage
      - /var/run/docker.sock:/var/run/docker.sock

Note: Replace /mnt2/raid0_pool/azuracast_data with the actual path to your Rockstor share if named differently. To verify the mount location, run ls /mnt2/raid0_pool/ in your terminal.

4

Deploy and Initialize

3–5 min

Click Deploy the stack. Portainer will pull the required images and start AzuraCast. Once complete, navigate to [http://192.168.1.101](http://192.168.1.101) in your browser to complete the initial admin account setup.

Key Considerations Before Deploying

Port 80 / 443 Conflicts

If Rockstor's web UI or another service (like Nginx Proxy Manager) is using port 80 or 443 on host IP 192.168.1.101, AzuraCast's web service will fail to bind to those ports. If you hit a port collision, change the published web ports in the compose file to - "8080:80" and - "8443:443", then access the interface at [http://192.168.1.101:8080](http://192.168.1.101:8080).

  • Storage Pool Selection: Avoid mounting AzuraCast data on /mnt2/ssd_pool as it is currently at 96% utilization (only 48 GB remaining). Map your volumes to /mnt2/raid0_pool (56% used, 8.1 TB available) for your station music libraries.

Where would you like to go next?

I have AzuraCast at Hostinger and at my home

(http://n6xre.duckdns.org:8888/admin) and at my home (http://192.168.1.101:8085/admin) on a Rockstor NAS (not configured yet)

--- When you're ready to set up external access on the new router:

  1. Assign a Static IP: Reserve 192.168.1.101 for the Rockstor NAS in your new router's DHCP Reservation settings so its internal IP never changes.
  2. Forward the Required Ports: Add port forwarding rules targeting 192.168.1.101 for:
  • Web UI: 8085 (TCP)
  • Stream: 8010 (TCP/UDP)
  • HTTPS: 8443 (TCP)
  1. Verify WAN IP: Check if your public IP address changed from 68.224.7.224 on the new router's WAN status page before testing.
    CAN I USE A TP-Link Archer AX1300 Dual-Band High-Speed Gigabit Wi-Fi 6 Router, works with all Internet Service Providers, WPA3 Security, Easy Setup via Tether App - Archer AX1300 (https://www.walmart.com/ip/TP-Link-Archer-AX1300-Router/18048265147) to do this?

Yes, the TP-Link Archer AX1300 will work for this. It supports Address Reservation (DHCP reservation), Virtual Servers / Port Forwarding, and WAN IP status monitoring through both its web administration interface and the TP-Link Tether app.

One specific adjustments is required for the default local IP range:

1. Match the Local Subnet Range

TP-Link routers default to the 192.168.0.x IP range out of the box, whereas your Rockstor NAS is set to 192.168.1.101.

  • Before setting up port forwards or reserving the IP, navigate to Advanced > Network > LAN in the router's web admin interface (or Network Settings in the Tether app).
  • Change the router's IP Address from 192.168.0.1 to 192.168.1.1 and save. The router will reboot and issue IP addresses on the 192.168.1.x subnet.

1.Configure DHCP Address Reservation:Prerequisite.

  1. Open a browser and log into the router interface at 192.168.1.1 (or use the Tether app).
  2. Go to Advanced > Network > DHCP Server > Address Reservation.
  3. Locate your Rockstor NAS in the connected devices list (or enter its MAC address manually).
  4. Set the reserved IP address to 192.168.1.101 and save.

Verification: Reboot or reconnect the NAS network interface and ensure running ip addr on Rockstor shows 192.168.1.101.

2.Add Port Forwarding Rules:

  1. Go to Advanced > NAT Forwarding > Port Forwarding (or Virtual Servers depending on firmware version).

  2. Click Add and create three distinct rules targeting IP 192.168.1.101:

    • Web UI: External Port 8085 / Internal Port 8085 — Protocol: TCP
    • Stream: External Port 8010 / Internal Port 8010 — Protocol: ALL (TCP/UDP)
    • HTTPS: External Port 8443 / Internal Port 8443 — Protocol: TCP

  3. Enable each rule and save changes.

Verification: Check the rule list to ensure all three entries show an Enabled status directed to 192.168.1.101.

3.Confirm Public WAN Status:

  1. Navigate to Advanced > Network > Status (or the main Dashboard in Tether).
  2. Check the WAN / Internet section to confirm your current public IP address.
  3. Verify whether it matches 68.224.7.224 or if Cox assigned a new dynamic WAN IP upon connecting the new router.

Verification: Access http://<WAN-IP>:8085/admin or http://<WAN-IP>:8010/listen.mp3 from an external network (such as a mobile hotspot) to confirm stream reachability.