Usage against existing plugin about logstash-plugin-dev HOT 3 CLOSED

Cool; though I think you'll want to use chown -R builder $pluginworkdir

Admittedly I haven't really considered the use-case of running this container as a tool, but only as a dev-container, as described in https://github.com/cameronkerrnz/logstash-plugin-dev

Currently /bin/bash is the default entrypoint, which means if you want to run a tool via docker run, remember to pass it as a -c (to bash). Eg:

docker run --rm -it -v ${PWD}:/work cameronkerrnz/logstash-plugin-dev:7.9
   -c "logstash-plugin generate --type=filter --name=coolstuff --path=/work/"

Thanks for your interest.

from logstash-plugin-dev.

If I execute the command from within the shell (no bundle install appended to the docker run command), it seems to work.

My requirement though was also to be able to build and include the plugin as part of another docker image so I am trying that now.

from logstash-plugin-dev.

FYI it worked great with the following,

FROM cameronkerrnz/logstash-plugin-dev:7.9 as logstash-builder

###############################
# Clone logstash-output-mongo #
###############################

USER root

ARG pluginworkdir=/work/logstash-output-mongodb

RUN git clone https://github.com/iteratec/logstash-output-mongodb \
        --branch feature/implementDifferentActions --single-branch $pluginworkdir
RUN chown builder $pluginworkdir

WORKDIR $pluginworkdir

USER builder
RUN bundle install \
    && bundle exec rspec \
    && gem build logstash-output-mongodb.gemspec

Closing this issue cause it seems the docker run is not a real blocker.

Thank you!

from logstash-plugin-dev.