Issue with Docker Startup

RE: Issue with Docker Startup

Nicholas Wurster — Wed, 23 Sep 2020 20:55:53 GMT

I have been able to reproduce the WSL v2 CRASHLOOPBACKOFF you describe and assuming that you resolved it by switching to Hyper-V. I am having issues with the Hyper-V option at the data server step and can't seem to get it working with either WSL v2 or HyperV - different fail points.

Any Hyper-V settings that you recall made a difference?

RE: Issue with Docker Startup

Jacob Edelman — Thu, 06 Aug 2020 15:47:13 GMT

I finally got it working but it was not easy. Had to eventually start the RDBMS container first and then start everything else separately...

Documentation doesn't provide any troubleshooting guidance and with the introduction of WSL backing on windows for Docker, it's not clear if using Hyper-V is better or not. Also, documentation says 5.1.47 is supported for MySQL connector but further down references 5.1.45.

RE: Issue with Docker Startup

Jacob Edelman — Mon, 03 Aug 2020 17:52:10 GMT

OK issue was using a win license when I have a linux VM. Got that resolved, but now there is an issue starting the rmdbs container.

web-application    | 2020-08-05 19:03:49 WARNING [wait-for-component] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
web-application    |    com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Access denied for user 'appian'@'%' to database 'AppianPrimaryDS'

Any ideas?

RE: Issue with Docker Startup

Jacob Edelman — Mon, 03 Aug 2020 14:25:27 GMT

I updated to Windows 10 Pro and turned off WSL2 support so it's using Hyper-V. I can configure the resource allocation fine, but it never goes above 1 GB of usage for the service-manager. I still get the same CRASHLOOPBACKOFF. Does anyone have this working on Windows? Anyway to troubleshoot this better?

RE: Issue with Docker Startup

Jacob Edelman — Sat, 01 Aug 2020 15:19:19 GMT

I think the issue is with Hyper-V and VM memory allocation. I am doing this on Windows 10 Home, and I was able to enable Hyper-V but I cannot change the amount of memory to be allocated (I think it's limited to 1 GB).

Has anyone gotten this working on Windows 10 Home?