Final Container Settings
We now need to make the installation permanent by setting up some final bits in Docker.
Head back into the Docker GUI and stop the Spotweb container, either by using the button or under ‘Action’ at the top of the UI
Once the container has stopped right click on it and click ‘Edit’ to get back into its settings.
Volume Settings
We can now move onto the ‘Volume Settings’ tab in which we will be specifying the directory where the main Spotweb settings file will be stored permanently.
Click on ‘Add Folder’ then select the ‘docker’ folder and create a new sub-folder called ‘spotweb’ select this folder and click ‘select’
Now add ‘/config’ to the Mount path box as per the screenshot below,
Next go back to the General Settings tab, and go into ‘Advanced Settings’
Environment Variables
We are now going to specify some additional variables.
Click the Add button, and fill in the following details as per the table/screenshot.
The two CRON tasks tells Spotweb to check for new releases every 15 minutes and a cache check takes place at 10 minutes past the hour.
| Variable | Value |
|---|---|
| TZ | Your timezone wikipedia.org/wiki/List_of_tz_database_time_zones |
| SPOTWEB_DB_TYPE | pdo_mysql |
| SPOTWEB_DB_HOST | YourNASIP |
| SPOTWEB_DB_PORT | 3306 |
| SPOTWEB_DB_NAME | spotweb |
| SPOTWEB_DB_USER | Your MariaDB username |
| SPOTWEB_DB_PASS | Your MariaDB password |
| SPOTWEB_CRON_RETRIEVE | */15 * * * * |
| SPOTWEB_CRON_CACHE_CHECK | 10 */1 * * * |
Click on Save to move back to the main screen then press save again to save all the changes, you can now start the container again.
After a minute or so you should be able to get into the WebUI by going to the IP of your NAS followed by port 9096
e.g http://192.168.0.30:9096/
See page 4 for the FAQ which I recommend checking out.
Throw me some bits or buy me a coffee?
If you have found my site useful please consider pinging me a tip as it helps cover the cost of running the site, you can even buy me a coffee 🙂
 |  |  |
Sorry I forgot to tell you that we had a power failure in our district yesterday night for about 2 hours. and after that this problem come up.
Hey, Did you have Spotweb running successfully before the power outage?
Yes it runs successfully, but now it won’t run because of mariadb did not work anymore. I have stopped both containers now. Waiting for a solution or help.
When I get home tonight I can help you get it up and running, are you able to join Discord so we can walk through? Helps me keep the solution for any else who has the issue. I think we can downgrade the database again. To a different release as you error log suggests it is unable to perform an upgrade.
Yes I am, I have Discord installed. The question is, when will you be at home? I am from Germany 🙂
Back about 5:30pm UK time.
Hi Dr_Frankenstein,
I have the same problem llike Chalky, mariadb ist starting and stopping the hole time. I have already checked the mount point, and it is set correctly by “File/Folder: /docker/mariadb”, “Mount-Point: /var/lib/mysql”.
The aria_log file in the mariadb follder includes a lot of entrys (notes and errors):
2022-05-27 20:29:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-05-27 20:29:24+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2022-05-27 20:29:24+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-05-27 20:29:24+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-05-27 20:29:24 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 …
2022-05-27 20:29:24 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-27 20:29:24 0 [Note] InnoDB: Number of transaction pools: 1
2022-05-27 20:29:24 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-05-27 20:29:24 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: check seccomp filters, and the kernel version (newer than 5.1 required)
2022-05-27 20:29:24 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2022-05-27 20:29:24 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-05-27 20:29:24 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-27 20:29:24 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.7.3.
2022-05-27 20:29:24 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-05-27 20:29:24 0 [Note] InnoDB: Starting shutdown…
2022-05-27 20:29:24 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
2022-05-27 20:29:24 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2022-05-27 20:29:24 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2022-05-27 20:29:24 0 [ERROR] Unknown/unsupported storage engine: InnoDB
I run Docker on a Synology NAS DS918+ with DSM 7.1-42661 Update 1.
I dont know how to sole this problem, could you please help?
Thank you
I had the same issue, I’m not sure what ended up causing it, but I just deleted the DB since I had nothing other than spotweb in it at that time. Hoping it doesn’t come up again, but I might just change the MariaDB version to fixed instead of latest to prevent any updates from occurring
I will come back in a bit, I will check what I set on my personal setup.
Hey xIExodusIx, sorry for the late reply I am catching up on some missed comments. Have you fixed this yet? If not reach out on Discord or via the Contact Me page under the logo for the site.
Hi Dr_Frankenstein, no i havn’t fixed it until now. I’m thinking about to delete the “mysql” Folder, but not did it until now. Sorry for my late response, I have not been at homme for about 2 Weeks and could not read your reply.
Are you able to reach out on Discord so we can setup a thread to talk through.