(Support) Aptalca's docker templates

aptalca · May 14, 2016

Fresh docker pull, fresh install, I'm getting this error:

* /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full!

Any suggestions? ZM v1.28 worked fine. I've tried this both upgrading the existing files (fails) and fresh (the error above.)

Thanks.

Your disk might be full

Flick · May 14, 2016

Your disk might be full

I deserved that. I should have specifically said that I did the obvious and checked free space. The disk, a 480GB SSD, is only 67% utilized. The Docker image file is set to 30GB and is using 20GB. Thanks.

aptalca · May 14, 2016

Your disk might be full

I deserved that. I should have specifically said that I did the obvious and checked free space. The disk, a 480GB SSD, is only 67% utilized. The Docker image file is set to 30GB and is using 20GB. Thanks.

Can you post the full log? When you install from scratch into a new config folder.

Flick · May 14, 2016

Can you post the full log? When you install from scratch into a new config folder.

Well poop. I deleted the config folder, which I'd done several times last night, and I fired the container back up. This time it worked! The only thing I can think of is that I did do an Unraid restart this morning as part of some maint I was doing. I apologize for wasting your time.

Now to see if I can point it at the old install and have it properly upgrade!

Flick · May 14, 2016

Now to see if I can point it at the old install and have it properly upgrade!

Fail:

php.ini already exists
using existing mysql database
using existing data directory
using existing perl data directory
creating symbolink links
setting the correct local time
increasing shared memory
starting services
* Starting MySQL database server mysqld
...done.
* Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly.
* Starting web server apache2
* 
Starting ZoneMinder: failure

php.ini already exists
using existing mysql database
using existing data directory
using existing perl data directory
creating symbolink links
setting the correct local time
increasing shared memory
starting services
* Starting MySQL database server mysqld
...done.
* Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly.
* Starting web server apache2
* 
Starting ZoneMinder: failure

That's me trying it twice. Suggestions?

aptalca · May 14, 2016

Can you post the full log? When you install from scratch into a new config folder.

Well poop. I deleted the config folder, which I'd done several times last night, and I fired the container back up. This time it worked! The only thing I can think of is that I did do an Unraid restart this morning as part of some maint I was doing. I apologize for wasting your time.

Now to see if I can point it at the old install and have it properly upgrade!

Version 1.29 is not meant to upgrade the old version to new.

It is a separate container because the changes between 1.28 and 1.29 break the container.

You should start from scratch with 1.29

Flick · May 14, 2016

Version 1.29 is not meant to upgrade the old version to new.

It is a separate container because the changes between 1.28 and 1.29 break the container.

You should start from scratch with 1.29

Ah, that would indeed explain it! I'd wondered why you'd gone down the path of two. I'll work on duplicating my settings so I can get the API going.

Thank you for your responsiveness!

johnm160 · May 15, 2016

I need some help with RDP-Calibre

I installed and it loads fine, I have a large library that I want stored outside of the container. I added the new path and added the variable like the instructions said but as soon as I do it shows up as an orphaned image.

Can someone please take a look and tell me what I did wrong?

JonathanM · May 15, 2016

I need some help with RDP-Calibre

I installed and it loads fine, I have a large library that I want stored outside of the container. I added the new path and added the variable like the instructions said but as soon as I do it shows up as an orphaned image.

Can someone please take a look and tell me what I did wrong?

Shot in the dark, but try it without a space in the folder name.

Squid · May 15, 2016

I need some help with RDP-Calibre

I installed and it loads fine, I have a large library that I want stored outside of the container. I added the new path and added the variable like the instructions said but as soon as I do it shows up as an orphaned image.

Can someone please take a look and tell me what I did wrong?

http://lime-technology.com/forum/index.php?topic=40937.msg463355#msg463355

Squid · May 15, 2016

I need some help with RDP-Calibre

I installed and it loads fine, I have a large library that I want stored outside of the container. I added the new path and added the variable like the instructions said but as soon as I do it shows up as an orphaned image.

Can someone please take a look and tell me what I did wrong?

Shot in the dark, but try it without a space in the folder name.

Same issue as what I posted, but updating the webUI is a better solution than changing the folder name

JonathanM · May 15, 2016

I need some help with RDP-Calibre

I installed and it loads fine, I have a large library that I want stored outside of the container. I added the new path and added the variable like the instructions said but as soon as I do it shows up as an orphaned image.

Can someone please take a look and tell me what I did wrong?

Shot in the dark, but try it without a space in the folder name.

Same issue as what I posted, but updating the webUI is a better solution than changing the folder name

Ahh, so the same issue exists on either host or container paths? I just figured trying to pass and use spaces in the container was going to cause other issues, since we don't know how the path variable is being handled inside the container. In this case, the host paths did NOT contain spaces, just the container path, and associated variable to point to said path.

johnm160 · May 15, 2016

AH Thank You Guys, I updated and it works perfect now.

johnm160 · May 15, 2016

Ok I spoke a little too soon, but this is a different problem. Going to 8080 and selecting calibre works fine, going to 8081 it still thinks the library is at /config so it finds no books and causes errors. Where can I fix this?

Squid · May 15, 2016

Ok I spoke a little too soon, but this is a different problem. Going to 8080 and selecting calibre works fine, going to 8081 it still thinks the library is at /config so it finds no books and causes errors. Where can I fix this?

You'll have to wait for aptalca or someone else who knows this app to pipe in

johnm160 · May 15, 2016

Thanks will do

-Edit to add screenshot incase it helps

aptalca · May 15, 2016

Thanks will do

-Edit to add screenshot incase it helps

Can you add a screenshot of your new settings?

Calibre server (8081) should open the library at the address defined by the libraryinternalpath variable

The books are imported into the config folder, not inside the container. Why don't you set the config folder to where you want to keep the library?

johnm160 · May 16, 2016

Thanks will do

-Edit to add screenshot incase it helps

Can you add a screenshot of your new settings?

Calibre server (8081) should open the library at the address defined by the libraryinternalpath variable

The books are imported into the config folder, not inside the container. Why don't you set the config folder to where you want to keep the library?

aptalca · May 16, 2016

Pretty sure the space in the path is causing issues.

Try setting the libraryinternalpath to "/Calibre\ Library" without the quotes. Leave the mount points as is

aptalca · May 23, 2016

I rebooted Unraid over the weekend and ZM 1.29 stopped working. Well, partly. When I try to open the GUI I get this:

"Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user"

Looking in the log, I see this:

May 23 10:45:55 dda6a36a1409 syslog-ng[736]: syslog-ng starting up; version='3.5.3'
May 23 10:45:55 dda6a36a1409 zma[661]: INF [in mode 3/1, warming up]
May 23 10:45:55 dda6a36a1409 zma[674]: INF [in mode 5/1, warming up]
May 23 10:45:56 dda6a36a1409 zma[698]: INF [in mode 3/1, warming up]
May 23 10:45:58 dda6a36a1409 zma[674]: INF [Front Drive: 026 - Opening new event 555, section start]
May 23 10:46:25 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:28 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
php.ini already exists
using existing mysql database
using existing data directory
using existing perl data directory
creating symbolink links
setting the correct local time
increasing shared memory
starting services
* Starting MySQL database server mysqld
...done.
* Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly.
* Starting web server apache2
* 
Starting ZoneMinder: success

May 23 10:45:55 dda6a36a1409 syslog-ng[736]: syslog-ng starting up; version='3.5.3'
May 23 10:45:55 dda6a36a1409 zma[661]: INF [in mode 3/1, warming up]
May 23 10:45:55 dda6a36a1409 zma[674]: INF [in mode 5/1, warming up]
May 23 10:45:56 dda6a36a1409 zma[698]: INF [in mode 3/1, warming up]
May 23 10:45:58 dda6a36a1409 zma[674]: INF [Front Drive: 026 - Opening new event 555, section start]
May 23 10:46:25 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:28 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:52 dda6a36a1409 web_php[534]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:47:10 dda6a36a1409 zmc[655]: INF [LaundryRoom: 1000 - Capturing at 13.16 fps]
May 23 10:47:10 dda6a36a1409 zma[661]: INF [LaundryRoom: 1000 - Analysing at 13.16 fps]
May 23 10:48:08 dda6a36a1409 zmc[670]: INF [Front Drive: 1000 - Capturing at 7.46 fps]
May 23 10:48:08 dda6a36a1409 zma[674]: INF [Front Drive: 1000 - Analysing at 7.46 fps]
May 23 10:48:13 dda6a36a1409 web_php[531]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:48:16 dda6a36a1409 web_php[531]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:48:28 dda6a36a1409 zmc[655]: INF [LaundryRoom: 2000 - Capturing at 12.82 fps]
May 23 10:48:28 dda6a36a1409 zma[661]: INF [LaundryRoom: 2000 - Analysing at 12.82 fps]
May 23 10:49:05 dda6a36a1409 zmc[688]: INF [GalaxyS3: 1000 - Capturing at 5.26 fps]
May 23 10:49:06 dda6a36a1409 zma[698]: INF [GalaxyS3: 1000 - Analysing at 5.24 fps]

I tried Googling but wasn't able to find anything useful. I hadn't made any changes to it at all so I don't know why it suddenly wouldn't write. I ran the "Update Permissions" utility in Unraid but to no avail.

Any help is appreciated. Thank you!

Never run the permissions utility on your docker container folders. That's probably what caused it.

While the container is running, exec into it and change the permissions. Make sure that the data folder is owned by www-data:www-data and the mysql folder is owned by mysql-mysql

Squid · May 23, 2016

I rebooted Unraid over the weekend and ZM 1.29 stopped working. Well, partly. When I try to open the GUI I get this:

"Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user"

Looking in the log, I see this:

May 23 10:45:55 dda6a36a1409 syslog-ng[736]: syslog-ng starting up; version='3.5.3'
May 23 10:45:55 dda6a36a1409 zma[661]: INF [in mode 3/1, warming up]
May 23 10:45:55 dda6a36a1409 zma[674]: INF [in mode 5/1, warming up]
May 23 10:45:56 dda6a36a1409 zma[698]: INF [in mode 3/1, warming up]
May 23 10:45:58 dda6a36a1409 zma[674]: INF [Front Drive: 026 - Opening new event 555, section start]
May 23 10:46:25 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:28 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
php.ini already exists
using existing mysql database
using existing data directory
using existing perl data directory
creating symbolink links
setting the correct local time
increasing shared memory
starting services
* Starting MySQL database server mysqld
...done.
* Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly.
* Starting web server apache2
* 
Starting ZoneMinder: success

May 23 10:45:55 dda6a36a1409 syslog-ng[736]: syslog-ng starting up; version='3.5.3'
May 23 10:45:55 dda6a36a1409 zma[661]: INF [in mode 3/1, warming up]
May 23 10:45:55 dda6a36a1409 zma[674]: INF [in mode 5/1, warming up]
May 23 10:45:56 dda6a36a1409 zma[698]: INF [in mode 3/1, warming up]
May 23 10:45:58 dda6a36a1409 zma[674]: INF [Front Drive: 026 - Opening new event 555, section start]
May 23 10:46:25 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:28 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:52 dda6a36a1409 web_php[534]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:47:10 dda6a36a1409 zmc[655]: INF [LaundryRoom: 1000 - Capturing at 13.16 fps]
May 23 10:47:10 dda6a36a1409 zma[661]: INF [LaundryRoom: 1000 - Analysing at 13.16 fps]
May 23 10:48:08 dda6a36a1409 zmc[670]: INF [Front Drive: 1000 - Capturing at 7.46 fps]
May 23 10:48:08 dda6a36a1409 zma[674]: INF [Front Drive: 1000 - Analysing at 7.46 fps]
May 23 10:48:13 dda6a36a1409 web_php[531]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:48:16 dda6a36a1409 web_php[531]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:48:28 dda6a36a1409 zmc[655]: INF [LaundryRoom: 2000 - Capturing at 12.82 fps]
May 23 10:48:28 dda6a36a1409 zma[661]: INF [LaundryRoom: 2000 - Analysing at 12.82 fps]
May 23 10:49:05 dda6a36a1409 zmc[688]: INF [GalaxyS3: 1000 - Capturing at 5.26 fps]
May 23 10:49:06 dda6a36a1409 zma[698]: INF [GalaxyS3: 1000 - Analysing at 5.24 fps]

I tried Googling but wasn't able to find anything useful. I hadn't made any changes to it at all so I don't know why it suddenly wouldn't write. I ran the "Update Permissions" utility in Unraid but to no avail.

Any help is appreciated. Thank you!

Never run the permissions utility on your docker container folders. That's probably what caused it.

While the container is running, exec into it and change the permissions. Make sure that the data folder is owned by www-data:www-data and the mysql folder is owned by mysql-mysql

Realistically, that's hard to avoid if you ever run the New Permissions tool as you cannot specify shares to exclude -> only disks. Would a better solution be to change the ownerships to whatever is required, similar to what lsio does when the container is run?

aptalca · May 23, 2016

I rebooted Unraid over the weekend and ZM 1.29 stopped working. Well, partly. When I try to open the GUI I get this:

"Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user"

Looking in the log, I see this:

May 23 10:45:55 dda6a36a1409 syslog-ng[736]: syslog-ng starting up; version='3.5.3'
May 23 10:45:55 dda6a36a1409 zma[661]: INF [in mode 3/1, warming up]
May 23 10:45:55 dda6a36a1409 zma[674]: INF [in mode 5/1, warming up]
May 23 10:45:56 dda6a36a1409 zma[698]: INF [in mode 3/1, warming up]
May 23 10:45:58 dda6a36a1409 zma[674]: INF [Front Drive: 026 - Opening new event 555, section start]
May 23 10:46:25 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:28 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
php.ini already exists
using existing mysql database
using existing data directory
using existing perl data directory
creating symbolink links
setting the correct local time
increasing shared memory
starting services
* Starting MySQL database server mysqld
...done.
* Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly.
* Starting web server apache2
* 
Starting ZoneMinder: success

May 23 10:45:55 dda6a36a1409 syslog-ng[736]: syslog-ng starting up; version='3.5.3'
May 23 10:45:55 dda6a36a1409 zma[661]: INF [in mode 3/1, warming up]
May 23 10:45:55 dda6a36a1409 zma[674]: INF [in mode 5/1, warming up]
May 23 10:45:56 dda6a36a1409 zma[698]: INF [in mode 3/1, warming up]
May 23 10:45:58 dda6a36a1409 zma[674]: INF [Front Drive: 026 - Opening new event 555, section start]
May 23 10:46:25 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:28 dda6a36a1409 web_php[530]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:46:52 dda6a36a1409 web_php[534]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:47:10 dda6a36a1409 zmc[655]: INF [LaundryRoom: 1000 - Capturing at 13.16 fps]
May 23 10:47:10 dda6a36a1409 zma[661]: INF [LaundryRoom: 1000 - Analysing at 13.16 fps]
May 23 10:48:08 dda6a36a1409 zmc[670]: INF [Front Drive: 1000 - Capturing at 7.46 fps]
May 23 10:48:08 dda6a36a1409 zma[674]: INF [Front Drive: 1000 - Analysing at 7.46 fps]
May 23 10:48:13 dda6a36a1409 web_php[531]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:48:16 dda6a36a1409 web_php[531]: FAT [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]
May 23 10:48:28 dda6a36a1409 zmc[655]: INF [LaundryRoom: 2000 - Capturing at 12.82 fps]
May 23 10:48:28 dda6a36a1409 zma[661]: INF [LaundryRoom: 2000 - Analysing at 12.82 fps]
May 23 10:49:05 dda6a36a1409 zmc[688]: INF [GalaxyS3: 1000 - Capturing at 5.26 fps]
May 23 10:49:06 dda6a36a1409 zma[698]: INF [GalaxyS3: 1000 - Analysing at 5.24 fps]

I tried Googling but wasn't able to find anything useful. I hadn't made any changes to it at all so I don't know why it suddenly wouldn't write. I ran the "Update Permissions" utility in Unraid but to no avail.

Any help is appreciated. Thank you!

Never run the permissions utility on your docker container folders. That's probably what caused it.

While the container is running, exec into it and change the permissions. Make sure that the data folder is owned by www-data:www-data and the mysql folder is owned by mysql-mysql

Realistically, that's hard to avoid if you ever run the New Permissions tool as you cannot specify shares to exclude -> only disks. Would a better solution be to change the ownerships to whatever is required, similar to what lsio does when the container is run?

You're right, but I thought that the permissions utility was only meant to be run when one first sets up unraid and transfers their files over rsync or something else that preserves permissions and ownership, or if they upgrade from an earlier version (4.7 I believe). I was never a big fan of it. It's like dropping a nuke to get rid of some weeds in the garden. Especially now with all the docker containers hosting their files in user shares. You wouldn't do chown -R on the entire filesystem of any linux flavor as it is bound to break things.

Squid · May 23, 2016

You're right, but I thought that the permissions utility was only meant to be run when one first sets up unraid and transfers their files over rsync or something else that preserves permissions and ownership, or if they upgrade from an earlier version (4.7 I believe). I was never a big fan of it. It's like dropping a nuke to get rid of some weeds in the garden. Especially now with all the docker containers hosting their files in user shares. You wouldn't do chown -R on the entire filesystem of any linux flavor as it is bound to break things.

You're correct there except that with unRaid running Docker, etc a misconfigured docker app can create folders / files within the array with wrong permissions / ownership that directly impacts the ability of the user to be able to manage the files (I'm sure we've all run across the "You need permission to perform this action" error from windows on a media file that just got downloaded), and running the New Perms tool is the recommended fix by many people here helping out. (Not to mention the easiest)

TBH, I think that part of the reason for the decision to have docker reside within an image file and not a separate folder on a BTRFS cache drive (as it was originally setup in unRaid 6 beta whatever) was because of the New Perms tools basically taking everything down.

I think that I'll post a feature req to have New Perms by default ignore the appdata folder...

bluepr0 · May 24, 2016

Hello!

I've seen that you have a Zoneminder docker... have you tried https://www.ivideon.com by any chance? It seems to have a very nice UI and feature set. It's supposedly free, as far as I've read.

aptalca · May 24, 2016

Hello!

I've seen that you have a Zoneminder docker... have you tried https://www.ivideon.com by any chance? It seems to have a very nice UI and feature set. It's supposedly free, as far as I've read.

It seems neat. I was able to install it on my test system with the rdp gui, but since I have no ip cams at the moment, I was not able to test it. I'll look into testing it with a public webcam when I have more time.

Installing it with cloud access is easy, but providing support would be challenging for folks who want to use it for local access only.

(Support) Aptalca's docker templates

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

aptalca

trurl

trurl

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation