Merry Christmas too, thanks a lot for your contribution. 🙏

Are we ready to merge or is there any more changes @gounthar @dduportal

From experiments with the jenkins/jenkins:2.375.1 container, I can remove a plugin from the installation by removing the entry from the plugins.txt file, building a new container image, then stopping the existing container and starting with the new container image.

Dockerfile that I used was:

FROM jenkins/jenkins:2.375.1
COPY --chown=jenkins:jenkins plugins.txt $REF/plugins.txt
RUN jenkins-plugin-cli --plugin-file $REF/plugins.txt

However, that simple use case does not cover the cases where the user is preserving their configuration in a separate data volume. In that case, then I believe that additional steps will be required in order to remove the files from $JENKINS_HOME/plugins/* so that the jenkins.sh script that starts the java -jar jenkins.war process is writing the set of plugins from the $REF directory to the plugins directory without having to remove existing files.

From experiments with the jenkins/jenkins:2.375.1 container, I can remove a plugin from the installation by removing the entry from the plugins.txt file, building a new container image, then stopping the existing container and starting with the new container image.

Dockerfile that I used was:

FROM jenkins/jenkins:2.375.1
COPY --chown=jenkins:jenkins plugins.txt $REF/plugins.txt
RUN jenkins-plugin-cli --plugin-file $REF/plugins.txt

However, that simple use case does not cover the cases where the user is preserving their configuration in a separate data volume. In that case, then I believe that additional steps will be required in order to remove the files from $JENKINS_HOME/plugins/* so that the jenkins.sh script that starts the java -jar jenkins.war process is writing the set of plugins from the $REF directory to the plugins directory without having to remove existing files.

Added a new commit- b0b6bcf

Let me know, if there are any suggestions.

Any update on this

Any update on this

Sorry for the delay. It will likely be a few more days before I can review.

Same for me, sorry.

@MarkEWaite can you help me with the new updates that I need to add or remove from this PR?

Most of this is general documentation that applies to all Jenkinses. Why is it added to the documentation of the Docker images?

Because it's needed here until a "general documentation with clear examples for Docker" is provided. There are multiple specific elements for Docker image that are required, which does NOT apply to packaged distribution of Jenkins (the fact that plugins should be pre-installed in the image in /usr/share/jenkins/ref but that what Jenkins sees is the data volume in /var/jenkins-home for instance.

Hey @dduportal, can you help me with this PR. Its been one month without any update from other maintainers.

Sorry for the delay @ritikbanger . I'll do my best to help with a review within the next 7 days. @dduportal probably won't be able to help due to other priorities that he needs to handle.

@dduportal I have updated the PR with your feedback. Please have a look.

@gounthar your review will be highly appreciated

@gounthar I think we are ready to merge this.

Thank you very much for your contribution and the latest changes, @ritikbanger.
I don't have the authority to merge your pull request, but I have already approved it.

@dduportal

Hi @ritikbanger , any news? This PR has been opened for quite some time and it would benefit from an update.

I would be updating this PR shortly.

Thanks. 🤗

@dduportal Please have a look.

@dduportal Please have a look.

Thanks @ritikbanger . I'll check before end of month as I only have low availability for now.

@dduportal Please have a look.

Thanks @ritikbanger . I'll check before end of month as I only have low availability for now.

Any update on this

Its been 2 years since this PR, if we are not merging it, kindly close it.

Hi @ritikbanger , many thanks for the content, work and pings. Sorry for not being able to take the required time.

it’s been a long time so i do not remember all the details, but reviewing it again (eg. From scratch) , i feel line this content should mostly be in www.jenkins.io as it is a good step by step which is oriented not only for Docker containers but also jenkins in general. And the readme here should point the user to the www.jenkins.io.
My past proposal to have a first step here seems unwise today as it would mean not spending the right effort.

wdyt @MarkEWaite @gounthar @kmartens27 ?

I believe this kind of information would be better suited for the jenkins.io website.

I agree with @gounthar that this would be very helpful information to have on jenkins.io, as uninstalling a plugin is a fairly common practice that would be good to have documented.

Could you share me which specific section of this repo should i put this into

Sure thing @ritikbanger! I think the Managing Plugins section of documentation would be the most appropriate. There is already a section for Removing/Uninstalling plugins, so this could be a unique section under that area with it's own "Uninstalling a plugin with Docker" header.

I agree with @kmartens27 suggestion. A subsection within the existing Uninstalling a Plugin page would indeed be an ideal location for this information.

When adding the new subsection, we should:

1. Ensure it complements the existing content without duplicating information.
2. Focus on providing additional, valuable insights specific to the topic at hand.
3. Maintain consistency with the current structure and style of the documentation.