[support] Bungy's docker repository


Recommended Posts

Bungy, do you remember our openHAB discussion? The docker is working now  :D

 

I just removed the TUNNEL definition in the KNX part of openhab.cfg.....that was doing the trick.

 

Will try now passing a zwave USB stick to the docker. I need cabman for that. Issue is here:

HTTP ERROR 404

Problem accessing /habmin. Reason:

    ProxyServlet: /habmin

 

Edgar,

 

Make sure that you are accessing using a url such as:

http://tower:8080/habmin/

 

Other then that, I would guess something is screwed up with either the addon(s) for habmin being deleted or the webapp altogether being deleted.

This is often a problem using java based applications - configurations get screwed up often and easily. I find openhab is extremely susceptible to errors in configuration.

 

I'm a bit slammed with work ATM, so the best thing I could do for you is to suggest starting the docker fresh, make sure you can access habmin, and slowly integrating your configuration back in.

Link to comment
  • 2 weeks later...

I have installed the OwnCloud container and can't get the page to load... The only thing in the log is

 

151221 10:14:21 mysqld_safe Logging to '/var/lib/mysql/cf9a8b1f797b.err'.
151221 10:14:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

 

Also, my data directories/mappings are empty after starting...

 

Thoughts?

Link to comment

I have installed the OwnCloud container and can't get the page to load... The only thing in the log is

 

151221 10:14:21 mysqld_safe Logging to '/var/lib/mysql/cf9a8b1f797b.err'.
151221 10:14:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

 

Thoughts?

 

Hmm... I'm having the same issue. I'm not actually the author of the docker - I just provided the template. Can you post an issue with him? https://github.com/l3iggs/docker-owncloud

Link to comment

If you file an issue with him, itmay be worth it to include th lgs in /var//lib/mysql/*.err

 

This is what mine looks like:

 

2015-12-21 10:29:14 47924972562880 [Note] /usr/bin/mysqld (mysqld 10.1.9-MariaDB-log) starting as process 128 ...
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: The InnoDB memory heap is disabled
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Memory barrier is not used
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Using Linux native AIO
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Using CPU crc32 instructions
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Completed initialization of buffer pool
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Highest supported file format is Barracuda.
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: The log sequence numbers 1616819 and 1616819 in ibdata files do not match the log sequence number 1616849 in the ib_logfiles!
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Database was not shutdown normally!
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Starting crash recovery.
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Restoring possible half-written data pages
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: from the doublewrite buffer...
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: 128 rollback segment(s) are active.
2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Waiting for purge to start
2015-12-21 10:29:15 47924972562880 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1616849
2015-12-21 10:29:16 47925289838336 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-12-21 10:29:16 47924972562880 [Note] Plugin 'FEEDBACK' is disabled.
2015-12-21 10:29:16 47924972562880 [Note] Recovering after a crash using mysql-bin
2015-12-21 10:29:16 47924972562880 [Note] Starting crash recovery...
2015-12-21 10:29:16 47924972562880 [Note] Crash recovery finished.
2015-12-21 10:29:16 47924972562880 [Warning] Failed to create a socket for IPv6 '::': errno: 97.
2015-12-21 10:29:16 47924972562880 [Note] Server socket created on IP: '0.0.0.0'.
2015-12-21 10:29:16 47924972562880 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.1.9-MariaDB-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server

Link to comment

Quick update - after a docker restart my owncloud came back up and running. I'm not sure what the issue was, but it looks to be working now. No telling how long it'll stay up for.

 

Looks like the certs aren't generating causing apache to not start...

 

[root@c4484faa4069 /]# apachectl start
AH00526: Syntax error on line 144 of /etc/httpd/conf/extra/httpd-ssl.conf:
SSLCertificateFile: file '/https/server.crt' does not exist or is empty

[root@c4484faa4069 /]# sh -c 'SUBJECT="/C=US/ST=CA/L=CITY/O=ORGANIZATION/OU=UNIT/CN=localhost" /etc/httpd/conf/genSSLKey.sh'  
[root@c4484faa4069 /]# cp /etc/httpd/conf/server.crt /https
[root@c4484faa4069 /]# cp /etc/httpd/conf/server.key /https
[root@c4484faa4069 /]#  apachectl restart
httpd not running, trying to start

 

After that I can access the webui.

 

I did notice that in your template the /https volume mapping is set to read-only. Not sure if that matters because of how I did this.

 

Deleted and restarted and set /https to read/write and had the same problem. Must be a problem with the image.

Link to comment

AAron,

 

He's definitely correct. You need to provide your own ssl certificates if you use the https mapping. Otherwise, you can exclude the mapping and it'll generate the certificates itself.

 

I provide my own ssl certificates because it is linked to my domain, but you can certainly use the genSSLKey script provided within the docker.

 

You can try running with the environment variables REGENRATESSL_CERT=true and SUBJECT=/C=US/ST=CA/L=CITY/O=ORGANIZATION/OU=UNIT/CN=localhost (change the values for your needs)

 

The first time you run with these, it'll create the ssl certs in /https and then you can remove those variables for the next run.

Link to comment
  • 2 weeks later...

Just an FYI for anyone using the MySQL docker to run the Kodi database: MySQL was recently updated to version 5.7 as the "official" version. As such, my Docker updated to 5.7 a few days ago and Kodi started having issues, as described here:

 

http://forum.kodi.tv/showthread.php?tid=247907

 

Rather than hack a MySQL 5.7 install to "act" like 5.6, I decided to try and get the Docker to pull down the 5.6 latest version instead of 5.7. Turns out it's as simple as setting the "Repository" value to:

 

mysql:5.6

 

...in the Docker's advanced settings view. BACK UP YOUR DATABASE FIRST, since you'll probably end up having to do a fresh MySQL install. Also, if you do a full dump backup and you're already on 5.7, you'll need to remove any entries that refer to the "sys" or "mysql" databases in the backup file.

Link to comment

AAron,

 

He's definitely correct. You need to provide your own ssl certificates if you use the https mapping. Otherwise, you can exclude the mapping and it'll generate the certificates itself.

 

I provide my own ssl certificates because it is linked to my domain, but you can certainly use the genSSLKey script provided within the docker.

 

You can try running with the environment variables REGENRATESSL_CERT=true and SUBJECT=/C=US/ST=CA/L=CITY/O=ORGANIZATION/OU=UNIT/CN=localhost (change the values for your needs)

 

The first time you run with these, it'll create the ssl certs in /https and then you can remove those variables for the next run.

 

Okay, I've been at his for a while. I'm not the brightest bulb when it comes to most of the commands and wants of this here machine. However, I've managed to get the container working. (by installing the container then going back in and removing the /http)

 

When I go back into my AppData folder and into certs there aren't any certs being generated (or atleast there are no files listed there).

Is that normal?

 

Also, I'd like to edit the config.php file. However, when I try to edit the file it gives me an error in notepad++ that it cannot open the file. I'm assuming due to some permissions settings. Also assuming those settings cannot be edited from the standard windows screen.

 

My main goal here is to be able to access my cloud information remotely (off the network), hence the need to edit config.php. I'm assuming the SSL certificates will provide a lil' bit of protection for my files as well as the standard ye 'ol password.

 

Aside from not putting my owncloud on the internet are there any other precautions I can take to further protect my systems and network? (the way I understand it is basically all i have to do to allow access is to just forward the port that i'm using for the cloud)

Link to comment

Hi

 

Has anyone had luck using the owncloud container from Bungy's docker repo?

(https://hub.docker.com/r/l3iggs/owncloud/) .

 

I have been trying for days to get it to work and finally have gotten to a point where i'm at a loss.

 

I tested and the image work with no shares attached (using the GUI or manually in terminal), but as soon as I add a volume mapping it breaks.

 

Will not let me access over HTTP or HTTPS, but when I log into the docker container I can access the mapped volumes no problem (and create files from inside the docker that is visible outside docker in the unraid gui/terminal/smb mounts)

 

I have also tried to run it as privileged, but no luck.

 

 

Any ideas?

 

EDIT: p.s. have also tried the other container available in gfjardim repo , no luck either

Link to comment

Hi

 

Yeah i fixed it and it is now working nicely  (duh.... had to rename my certificate files ...)

 

Also, out of the box do you get a warning about the mem cache not being set?

"No memory cache has been configured. To enhance your performance please configure a memcache if available. Further information can be found in our documentation."

Link to comment

tested owncloud install 7 times in my 2 Unrsiad 6.1.7 servers today. All plugin settings by default. No luck - owncloud unreachable on port 8000.

 

Only two files in  /mnt/user/appdata/owncloud

 

server.key

server.pem

 

No configs, etc.

 

logfile:

No pre-existing certificate found, generating a new one with subject:

/C=US/ST=CA/L=City/O=Organization/OU=Organization Unit/CN=yourhome.com

ca-bundle.crt

fix_config.php

server.key

server.pem

Creating DH Parameters File

 

Link to comment

tested owncloud install 7 times in my 2 Unrsiad 6.1.7 servers today. All plugin settings by default. No luck - owncloud unreachable on port 8000.

 

Only two files in  /mnt/user/appdata/owncloud

 

server.key

server.pem

 

No configs, etc.

 

logfile:

No pre-existing certificate found, generating a new one with subject:

/C=US/ST=CA/L=City/O=Organization/OU=Organization Unit/CN=yourhome.com

ca-bundle.crt

fix_config.php

server.key

server.pem

Creating DH Parameters File

 

 

The proper way to include your own certificate files are to put them inside of a directory and map that directory to /https in the container.

 

Other then that, are there any files popping up in your configuration directory? Also can you post which volumes you're mapping?

Link to comment
  • 2 weeks later...

So, I'm a avid windows server user, and recently switched over to unraid. I am still wet behind the ears with navigating unraid via putty sessions.

 

I have loaded the bungy MySql docker via his template.

 

I figured out how to use the advanced settings to name my root password.

 

But now I am stuck, I need to configure the typical settings to allow Kodi to read/write with full permissions as per the wiki, which I have typically done in the windows command line tool for mysql with no issues.

 

I have loaded up a putty instance, and tried running the commands as described at https://hub.docker.com/_/mysql/

 

When trying the following:

docker run -it --link mysql:mysql --rm mysql sh -c 'exec mysql -h"10.x.x.x" -P"3306" -uroot -p"mypw"'

 

"mysql: [Warning] Using a password on the command line interface can be insecure.

ERROR 1045 (28000): Access denied for user 'root'@'172.17.42.1' (using password: YES)"

 

 

I have had quite the successful move to unraid with Plexserver, Sonarr, CouchPotato and Sabnzbd running with no issues. Having a successful mysql instance running so I can deploy my kodi players and sync everything with ease!!

Link to comment

So, I'm a avid windows server user, and recently switched over to unraid. I am still wet behind the ears with navigating unraid via putty sessions.

 

I have loaded the bungy MySql docker via his template.

 

I figured out how to use the advanced settings to name my root password.

 

But now I am stuck, I need to configure the typical settings to allow Kodi to read/write with full permissions as per the wiki, which I have typically done in the windows command line tool for mysql with no issues.

 

I have loaded up a putty instance, and tried running the commands as described at https://hub.docker.com/_/mysql/

 

When trying the following:

docker run -it --link mysql:mysql --rm mysql sh -c 'exec mysql -h"10.x.x.x" -P"3306" -uroot -p"mypw"'

 

"mysql: [Warning] Using a password on the command line interface can be insecure.

ERROR 1045 (28000): Access denied for user 'root'@'172.17.42.1' (using password: YES)"

 

 

I have had quite the successful move to unraid with Plexserver, Sonarr, CouchPotato and Sabnzbd running with no issues. Having a successful mysql instance running so I can deploy my kodi players and sync everything with ease!!

 

So what that command is doing is creating a 2nd mysql docker and trying to connect othe the first one with it. My guess is the permissions table on your docker isn't allowing connections from anywhere but 127.0.0.1, but the ip address of your new temporary docker is 172.17.42.1. Try this instead:

 

# This will get you into the shell of the mysql docker
docker exec -it mysql bash

mysql -u root -p
# Then enter your password

 

Give that a shot and let me know how it works for ya.

Link to comment

So, I'm a avid windows server user, and recently switched over to unraid. I am still wet behind the ears with navigating unraid via putty sessions.

 

I have loaded the bungy MySql docker via his template.

 

I figured out how to use the advanced settings to name my root password.

 

But now I am stuck, I need to configure the typical settings to allow Kodi to read/write with full permissions as per the wiki, which I have typically done in the windows command line tool for mysql with no issues.

 

I have loaded up a putty instance, and tried running the commands as described at https://hub.docker.com/_/mysql/

 

When trying the following:

docker run -it --link mysql:mysql --rm mysql sh -c 'exec mysql -h"10.x.x.x" -P"3306" -uroot -p"mypw"'

 

"mysql: [Warning] Using a password on the command line interface can be insecure.

ERROR 1045 (28000): Access denied for user 'root'@'172.17.42.1' (using password: YES)"

 

 

I have had quite the successful move to unraid with Plexserver, Sonarr, CouchPotato and Sabnzbd running with no issues. Having a successful mysql instance running so I can deploy my kodi players and sync everything with ease!!

 

So what that command is doing is creating a 2nd mysql docker and trying to connect othe the first one with it. My guess is the permissions table on your docker isn't allowing connections from anywhere but 127.0.0.1, but the ip address of your new temporary docker is 172.17.42.1. Try this instead:

 

# This will get you into the shell of the mysql docker
docker exec -it mysql bash

mysql -u root -p
# Then enter your password

 

Give that a shot and let me know how it works for ya.

 

Here's the result, I have gotten similar results with HeidiSQL, same error that is.

root@HORTA-unRaid:~# docker exec -it mysql bash
root@4c46fbbf6f82:/# mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
root@4c46fbbf6f82:/#

 

Link to comment

So, I'm a avid windows server user, and recently switched over to unraid. I am still wet behind the ears with navigating unraid via putty sessions.

 

I have loaded the bungy MySql docker via his template.

 

I figured out how to use the advanced settings to name my root password.

 

But now I am stuck, I need to configure the typical settings to allow Kodi to read/write with full permissions as per the wiki, which I have typically done in the windows command line tool for mysql with no issues.

 

I have loaded up a putty instance, and tried running the commands as described at https://hub.docker.com/_/mysql/

 

When trying the following:

docker run -it --link mysql:mysql --rm mysql sh -c 'exec mysql -h"10.x.x.x" -P"3306" -uroot -p"mypw"'

 

"mysql: [Warning] Using a password on the command line interface can be insecure.

ERROR 1045 (28000): Access denied for user 'root'@'172.17.42.1' (using password: YES)"

 

 

I have had quite the successful move to unraid with Plexserver, Sonarr, CouchPotato and Sabnzbd running with no issues. Having a successful mysql instance running so I can deploy my kodi players and sync everything with ease!!

 

So what that command is doing is creating a 2nd mysql docker and trying to connect othe the first one with it. My guess is the permissions table on your docker isn't allowing connections from anywhere but 127.0.0.1, but the ip address of your new temporary docker is 172.17.42.1. Try this instead:

 

# This will get you into the shell of the mysql docker
docker exec -it mysql bash

mysql -u root -p
# Then enter your password

 

Give that a shot and let me know how it works for ya.

 

Here's the result, I have gotten similar results with HeidiSQL, same error that is.

root@HORTA-unRaid:~# docker exec -it mysql bash
root@4c46fbbf6f82:/# mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
root@4c46fbbf6f82:/#

 

I just tried it out on my machine and it works. First command to initiate the mysql container:

docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql

 

2nd command to connect to the mysql instance:

docker run -it --link some-mysql:mysql --rm mysql sh -c 'exec mysql -hmysql -uroot -pmy-secret-pw'

Link to comment

I have tried uninstalling/reinstalling, different password variables, now trying a different network variable (host vs bridge).

 

Still having access denied errors. Could my volume mappings be an issue by any chance? I have all shares set to public, not sure what on earth I could be doing wrong.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.