docker-jenkins | Jenkins 2 in Docker , with pre-installed Docker | Continuous Deployment library

Created dockerfile with COPY ./cacerts /usr/local/openjdk-8/jre/lib/security/ command, Now Jenkins and Slack connection works.

Try to replace

This one is easy.

set AssociatePublicIpAddress to false.

You have a number of problems going on. As you said, you are using jenkins:2.190.2 but your plugins list is from: jenkins:1.647 (2016/02/04). A lot has changed, not just in the major bump, but in each LTS as well and in the plugins.

docker/plugins.sh has been superseded by docker/install-plugins.sh. Usage here.

echo "WARN: plugins.sh is deprecated, please switch to install-plugins.sh"

install-plugins.sh will resolve and download all dependencies for your plugins (each plugin list lists them in the details on the site), so your managed list can be much shorter. Just list the top-level plugins you need and it will resolve all dependencies. Maven plugins have progressively dropped unused dependencies as well.

NB: if you want a known configuration (not latest), run once with the master list using latest, then check-in that and the resolved list. Feed the resolved list to docker instance.

You can use this script to simplify your list:

Docker package creates the docker group on installation. Meanwhile, this is created with default values (which I did not take time to check, but my two ubuntu machines are running with a gid of 999).

In your above example, the group is created before installing the package with a default gid of 497 that can be customized (by setting DOCKER_GID in the docker environment). And there is a comment on you original link saying:

Set to 497 by default, which is the group ID used by AWS Linux ECS Instance

What you are building here is some sort of dind (docker in docker). The goal is to make sure that docker guid on the host is the same as the guid in the dind instance so that they can share files on mounted volumes (e.g. control sockets to launch other docker containers directly on the host generally...).

If you don't create the group beforehand, you cannot run groupadd afterwards because the group already exists.

You could run groupmod though on the existing group but I don't like to mess with [g|u]ids. Creating the system user/group with your exact requirements prior to installing your package is ususally the safest way to go.

/var/run/docker.sock in the container is the host's Docker socket, and nothing else. This is because:

1. A Docker container doesn't run any programs other than what's explicitly started in its entrypoint and/or command, and that's almost always just a single application program.
2. You're presumably not going out of your way to start the Docker daemon, so it's installed but not running.
3. Unix socket files won't get created until a daemon starts up and it bind(2) a socket to the specific file.
4. The docker run -v option will always "push" the host's content into the container, and this happens before any of the container processes run.

So in the scenario you're describing, it can't be anything other than the host Docker socket, because there isn't a second Docker daemon.

Let's say for the sake of argument that you actually are starting a second daemon this way.

The order of operations here is (1) Docker sets up the container filesystem, (2) Docker starts running the entrypoint, (3) the entrypoint starts the daemon, (4) the daemon tries to create the socket file. At the point where the daemon starts up, its socket file will already exist. I believe that will cause the bind(2) call to fail with EADDRINUSE, and the daemon won't start up. Hopefully this will cause your container startup to fail.

You could legitimately want to start a daemon in a container, that publishes a Unix socket, that you want to access from the host. To make this work you need to mount a directory into the container, and point the daemon at it. It probably can't be /var/run on either side (there's a lot of stuff in the host /var/run; mounting the directory hides the existing contents in the container and you could want the container's /var/run too). It must be a directory and not a socket filename since Docker will create an empty directory if it doesn't exist; something will exist in the container at that path and the bind will fail.

So if you wanted to start a hypothetical foo daemon inside a container, it would look roughly like

I've installed .NET Framework separately and it works now. Full Dockerfile

You need to run docker in docker.

So, in a nutshell, you mount the host docker socket as a volume into Jenkins and have compatible docker binaries in your container.

This is a good description

There is much more to it to consider, such as security depending on other containers running on your host and also how to run it when using jenkins agents.

So all Groovy scripting in Jenkins is a very thin layer over the actual Java objects, so to find the right constructor, we need to look at the code for the plugin: https://github.com/jenkinsci/active-directory-plugin/blob/1b082cbfb7d236d326c218c7b474fb51cb930080/src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java#L224-L270

If we take the first constructor as an example: