-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support publishing as Docker Engine managed plugin #96
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Olli Janatuinen <[email protected]>
45e1971
to
bac86e5
Compare
@olljanat This is great! Thanks for opening this PR. I am trying to run the
|
@shishir-a412ed that install command will only works after image is build and published to Docker Hub by this project maintainer(s). Before that you need build it using command which I added to CircleCI file. |
@olljanat Thanks for the tip! I will check and update soon. |
Any progress on this? I'd really like to avoid needing to |
@olljanat @virtualdxs Apologies for the delayed response! We were shut down the last 2 weeks (Christmas and New Year). |
@olljanat In the
Seems like the test is failing but just returning |
@olljanat I was able to build the plugin
Just FYI: The repository (shm32/docker-lvm-plugin:1.0) is Also, there are no instructions in there. Can you give me the commands (and the order in which they need to be executed) in order for me to build the plugin and try it out? |
@shishir-a412ed this stuff looks that you have build is as normal container, not as plugin because So plz remove that tag and actually whole
then Official documentation is available on https://docs.docker.com/engine/extend/#developing-a-plugin |
@olljanat Thank you for those instructions! Those were really helpful. I was able to remove the existing plugin both from my Then as per your instructions, I created the plugin and pushed it to the docker hub.
Just curious when you were testing it, did you had |
I've taken some interest in getting this working. I've had a thought about the problem and I think it may be down to the "on-demand socket activated" nature of the plugin. One note worthy thing I will try to sort this out with my own pull request, |
Fork and clone it normally and then fetch my branch as starting point with: git remote add olljanat https://github.com/olljanat/docker-lvm-plugin
git fetch olljanat
git checkout olljanat/docker-hub-support But as there is just couple of files you can easily copy those also. |
I have found my first error, maybe some additional packages for syslog are required in the container, |
I have managed to get the plugin to start as a container after changing the logging library from log/syslog to log |
moby/moby#33009 is holding me back at the moment, |
I collected need files based @nickbreen great work on https://github.com/nickbreen/docker-lvm-plugin , tested that it works, updated CI and readme.
Will allow you close #66