wallop 1 Report post Posted May 23, 2017 (edited) I'm trying to continue the work done by airtonix etc in making a docker friendly exile setup. My new arma 3 docker image is working great, but when I wire up the volumes with exile files and connect, I spawn in the grass and no keybinds work, similar to this post . I suspect this is a DB issue, though I am able to connect from arma container to the mysql db container on the cli, and all of the tables are created, it seems that extDB2 is never initialized (no logs etc). I also turned off strict mode in mysql - see docker-compose.yml RPT - https://ghostbin.com/paste/zjz22 To replicate: Quote git clone https://github.com/wallopthecat/docker-arma3-exile ./build.sh docker-compose up this works to connect to the db from the server container, where db is the hostname of mysql container Quote mysql -h db -u exile -p server_1 | 14:39:31 Player Blah connected (id=). server_1 | 14:39:31 BattlEye Server: Verified GUID () of player #0 blah server_1 | Unaccessible server_1 | 14:39:36 Server: Object 4:62 not found (message Type_121) server_1 | 14:39:36 Server: Object 4:51 not found (message Type_121) server_1 | 14:39:36 Server: Object 4:52 not found (message Type_121) server_1 | 14:39:36 Server: Object 4:53 not found (message Type_121) etc I did an `ldd extDB2.so` and all of the needed libs were loaded ok Edited May 25, 2017 by wallop Share this post Link to post Share on other sites
SombreFou 0 Report post Posted May 23, 2017 I have exactly the same problem as you. I do not understand how you solved. can you help me ? Share this post Link to post Share on other sites
flyingdutchmen 39 Report post Posted May 23, 2017 1 hour ago, SombreFou said: I have exactly the same problem as you. I do not understand how you solved. can you help me ? He didnt solve anything yet. We're working on it. Share this post Link to post Share on other sites
wallop 1 Report post Posted May 24, 2017 Dug in some more and found my params were off - I had `servermods` instead of `servermod`. After fixing that, this is the extDB2 log I get: extDB2: Failed to Load Protocol: SQL_CUSTOM_V2 That lead me to and after running my build script again without messing with casing - everything works great. Share this post Link to post Share on other sites