Taddeusz

I have 1.0.0-RC1 images ready to test! I have two images. One with MariaDB and one without. You may install them by changing the Repsitory on your Docker container to jasonbean/guacamole:1.0.0-RC1 for the image with MariaDB and jasonbean/guacamole:1.0.0-RC1-nomariadb without MariaDB. For the image that includes MariaDB you can still choose to use an external instance of MariaDB/MySQL by setting the variable OPT_MYSQL_EXTENSION=Y and set OPT_MYSQL=N and it will keep the extension but not load MariaDB. The image without MariaDB will load the MySQL extension with the original OPT_MYSQL=Y variable. Your guacamole.properties must be configured for a MariaDB/MySQL instance outside this container for either of these to work. For now I'm not going to provide a way to set up or upgrade an external MariaDB/MySQL instance since there's no way for me to know your database's version. So unless you really know what you're doing you should probably stick with the internal MariaDB. For those who wish to try your hand the Guacamole schema files are located in your appdata folder when you have enabled the MySQL extension. You just need to create a database, a user that has SELECT, INSERT, UPDATE, & DELETE permissions to that database, and apply the two schema files to the database you created. Once you modify your guacamole.properties file for that database it should work. I have switched my personal Guacamole instance over and as far as I can tell it works perfectly. I'm actually using the image without MariaDB.

I just wanted to update everyone on 1.0.0. I've taken some time over my holiday break to work on updating my Guacamole Docker with RC1. Thanks to the Guacamole team I've got a better build process. It looks like I'm going to be able to shave off about 120MB from the image size. I've also implemented a service manager and as a result I'm also able to not start the MariaDB service if you so choose. I'll also have an option to load just the MySQL extension so that you can use an external MySQL/MariaDB instance without the extra memory overhead in the current implementation. I have a few things to iron out but I think I should have 1.0.0-RC1 available for anyone to test in the next week or so.

Currently Python is not included in this container so it wouldn't be able to run. I'm not sure how much larger adding python would make it. I'm hesitant since it's already a really large container. Also, adding an interface to manage MAC addresses is not trivial. I also don't see where the script should be placed so that it will run on every connection attempt. They've recently released 1.0.0-RC1 so I'm going to be putting what time I have to implementing the new version. Feel free to clone my git repository. I will take a look at any pull requests. 1.0.0 is a huge change to the Dockerfile so any changes likely aren't going to be applicable.

Ok, maybe I'm wrong about changing the entry point. It looks like the default entry point is "/guacamole". Here doc page that talks about proxying on Nginx: http://guacamole.apache.org/doc/gug/proxying-guacamole.html#nginx. Are you only proxying Guacamole? Just wondering why you need to worry about the root?

I have a bunch of different location paths. Here is an excerpt from mine showing the location for Guacamole. This isn't my whole config file. I basically followed the Guacamole docs. I also modified my Guacamole config so that the entry point is /guacamole. It makes proxying much easier. Also, the "proxy_buffering off" is very important as having it on can make your connections not work. map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { location ^~ /guacamole/ { proxy_pass http://<sanitized ip>:<sanitized port>/guacamole/; proxy_buffering off; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; access_log off; } }

As far as I know you can only do this with Intel CPU's. The set up is the same as for Plex. You load the i915 driver and pass "--device /dev/dri" in extra parameters for the Docker application.

I once had lunch at Carl's Jr and ordered stuff that with tax all added up to $6.66. The lady taking my order looked at me with genuine fear and asked if I wanted anything else and I said I didn't. She took my money and then said: "Why you do this to me?" Let's just say I'm neither superstitious nor religious. It saddens me that people derive fear from a simple set of numbers.

You're probably going to kick yourself when I tell you this but move your hostname and port from the "proxy parameters" section down to the "parameters" section. That will fix it.

What was the error message you received on the screen when you tried to connect? What do your connection settings for this connection look like in Guacamole?

Yes, I have an i5 8400 Coffee Lake CPU so "H.265 10-bit (Intel QSV)" is also listed. It is working fine as well.

It's still working as expected.

Looks like it's working like it should now. H.264 QSV encoding is even working without the distortion.

I can't actually get it to work in any other preset other than "quality". If I try "speed" or "balanced" it makes one of my cores go to 100% and nothing happens.

Ok, I tried beta 3 and still got the same error on the second file. BTW, H.264 QSV encoding is still distorted.

Second encode still failed with the "libva info: va_getDriverName() returns 1" error.

Ok, that's what I queued up. 👍

Ok, I've started a test. Going to take longer than normal because my wife is watching Plex at the same time. It's configured for QSV as well. Nice that the fixed function hardware can multitask different applications.

That shouldn’t cause an issue. I also have a Mariahdb Docker running separately for another application. Could you post your catalina.out and Docker console log.

Does it show an error message that says "Invalid Login"?

I'm glad you narrowed down the problem. It's always fun trying to track down weird problems like this.

I realize QSV isn't really about quality. I tried that video but apparently in later versions of Handbrake they removed the "Extra Settings" box when you select a QSV encoder. Here is the output from the log when the HEVC encoder fails after finishing a previous encode: [16:36:21] scan: decoding previews for title 1 [16:36:21] scan: audio 0x1: dca, rate=48000Hz, bitrate=1536000 English (DTS-HD MA) (5.1 ch) [16:36:23] scan: 10 previews, 1920x1080, 23.976 fps, autocrop = 138/138/0/0, aspect 16:9, PAR 1:1 [16:36:23] scan: supported video decoders: avcodec qsv [16:36:23] libhb: scan thread found 1 valid title(s) [16:36:23] starting job [16:36:23] job configuration: [16:36:23] * source [16:36:23] + /storage/Output/Atomic_Blonde/Atomic_Blonde_t00.mkv [16:36:23] + title 1, chapter(s) 1 to 2 [16:36:23] + container: matroska,webm [16:36:23] * destination [16:36:23] + /output/Atomic_Blonde_t01.mkv [16:36:23] + container: Matroska (libavformat) [16:36:23] + chapter markers [16:36:23] * video track [16:36:23] + decoder: h264 [16:36:23] + filters [16:36:23] + Framerate Shaper (mode=1) [16:36:23] + frame rate: 23.976 fps -> constant 23.976 fps [16:36:23] + Crop and Scale (width=1920:height=804:crop-top=138:crop-bottom=138:crop-left=0:crop-right=0) [16:36:23] + source: 1920 * 1080, crop (138/138/0/0): 1920 * 804, scale: 1920 * 804 [16:36:23] + Output geometry [16:36:23] + storage dimensions: 1920 x 804 [16:36:23] + pixel aspect ratio: 1 : 1 [16:36:23] + display dimensions: 1920 x 804 [16:36:23] + encoder: H.265 (Intel Media SDK) [16:36:23] + preset: quality [16:36:23] + profile: auto [16:36:23] + level: auto [16:36:23] + quality: 15.00 (QP) [16:36:23] * audio track 1 [16:36:23] + decoder: English (DTS-HD MA) (5.1 ch) (track 1, id 0x1) [16:36:23] + bitrate: 1536 kbps, samplerate: 48000 Hz [16:36:23] + mixdown: 5.1 Channels [16:36:23] + encoder: AC3 (libavcodec) [16:36:23] + bitrate: 640 kbps, samplerate: 48000 Hz [16:36:23] sync: expecting 15900 video frames libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 1 libva error: va_getDriverName() failed with operation failed,driver_name=i965 [16:36:23] encqsvInit: MFXVideoENCODE_Init failed (-16) [16:36:23] Failure to initialise thread 'Quick Sync Video encoder (Intel Media SDK)' [16:36:23] vfr: 0 frames output, 0 dropped and 0 duped for CFR/PFR [16:36:23] vfr: lost time: 0 (0 frames) [16:36:23] vfr: gained time: 0 (0 frames) (0 not accounted for) [16:36:23] dca-decoder done: 0 frames, 0 decoder errors [16:36:23] h264-decoder done: 0 frames, 0 decoder errors [16:36:23] sync: got 0 frames, 15900 expected [16:36:23] libhb: work result = 3

Has anyone been doing QuickSync accelerated encoding with this docker? I first tried with my Ivy Bridge i5 3470 but the quality was really not good. I recently upgraded to a Coffee Lake i5 8400 and tried again. I’m getting horrible results. Basically every second or so the video jumps and there’s a distortion in it. I also tried the QSV accelerated HEVC encoding and while it works great and seems to look great I have to restart the container after every encode because every subsequent QSV HEVC encode fails. Just curious what everyone else’s experience is with this?

I just tested a clean install of this on my Unraid machine and it worked fine. I don't see anything that jumps out at me in your logs. Can you post your guacamole.config file and a screenshot of your Docker's configuration.

I’m at a conference today so I’m away from a computer. The first thing to try is stop the container, delete the ApacheGuacamole folder from your appears folder, then restart Guacamole. If that doesn't work post the output from the Guacamole Docker log and your catalina.out file. That last file is located in guacamole/log.