Application mount points are not supported during the runc creation

Created a Docker with an application on it, se the application as an ENTRYPOINT and it works fine with all the supporting databases it needs to pull from to get the data. What I am seeing is now the databases are not getting called and they the data come back is the basic response from the application.

So I started the a runc exec test /bin/bash to see what was going on in the system and the directories I need to program to have access to that would allow it to pull data was denied. I then looked for the ENTRYPOINT for the program and found that the program was accessible, but provided be the basic data back just if I were to run: runc exec test

The folders where I had my data during the build was /root/ for the sake of spinning it up quick. If I need to take extra steps and install users and permissions I will do that. I also noticed the "mounts": in the config.json can I just add the directories needed to that location and then where is the API for the creation of this file.

Thanks

Review the runc creation path and the config.json mounts section first; the issue provides no source file or test entry point. Reproduce the described Docker ENTRYPOINT and database-backed application, then verify that the required directories are mounted and the application returns its database-backed data.