Alright, so I was finally successful.
I ended up having to modify the resource.json file outside of the docker container and put it back in. Then I logged into the container with bash and performed a chown command to the json to make sure it matches the already there config.json owner:group.
Once I did this for the “/usr/local/bin/ignition/data/config/resources/core/ignition/database-connection/CONNECTIONNAMEFOLDER” and also to the “/usr/local/bin/ignition/data/config/resources/core/ignition/database-driver/DRIVERNAMEFOLDER” path, I was finally able to load the resource.
Also note: I modified both “web.xml” files accordingly
…and I still cannot up load the 80mb .jar file from snowflake without getting an http: 413 error. The only resolution is to again cp the file into the container using the “docker cp” command and again performing a chmod and chown to the .jar file to match the other files in the directory.
BTW if anyone is struggling to perform these commands inside the container, you have to login as root:
$ docker exec -u root -it CONTAINERNAME /bin/bash
Then you can perform the chown and chmod. What I still can’t do which is very frustrating, is perform either a nano or vim edit to any files from inside of the container. I have to move them out first and then modify them, to move them back in. It’s quite frustrating. But at least now I have connection!
