unterstein
commented
7 years ago Hey @kohend,
thanks for you pushed docker image dkohen/debug:minimesos. I started searching in your output --plugin_dir /marathon/plugin --plugin_conf /marathon/plugin-conf.json and will sum up what I found inside your image:
root@7f3cc99cbf4e:/marathon# ls -la /marathon/plugin
total 12
drwxr-xr-x 2 root root 4096 Jul 13 07:58 .
drwxr-xr-x 17 root root 4096 Jul 13 07:58 ..
-rw-r--r-- 1 root root 289 Jul 3 13:37 plugins_2.11-0.1-SNAPSHOT.jar
root@7f3cc99cbf4e:/marathon# cd plugin
root@7f3cc99cbf4e:/marathon/plugin# unzip plugins_2.11-0.1-SNAPSHOT.jar
Archive: plugins_2.11-0.1-SNAPSHOT.jar
inflating: META-INF/MANIFEST.MF
root@7f3cc99cbf4e:/marathon/plugin# ls
META-INF plugins_2.11-0.1-SNAPSHOT.jar
root@7f3cc99cbf4e:/marathon/plugin# ls META-INF/
MANIFEST.MF
root@7f3cc99cbf4e:/marathon/plugin# cat /marathon/plugin-conf.json
{
"plugins": {
"envVarExtender": {
"plugin": "mesosphere.marathon.plugin.task.RunSpecTaskProcessor",
"implementation": "mesosphere.marathon.example.plugin.env.EnvVarExtenderPlugin",
"configuration": {
"env": {
"foo": "bar",
"key": "value"
}
}
}
}
}
root@7f3cc99cbf4e:/marathon/plugin# As far as I can see, the provided plugin jar file is nearly empty. So probably something with the build process is not working properly. Can you verify that this file is empty (except the MANIFEST) on your box as well and explain how you build the jar?
Thanks Johannes
kohend
sudocurse
bennyyu686
I tried to add the jar file and the config file to the Marathon Docker image of minimesos and it seems to fail in loading the plugin despite the config being read properly (from what I can tell) and the file seen by Marathon.
I also added the directory that the plugin is in to the class path.