docker-files | This repo hosts docker files used by pulsarIO | Continuous Deployment library

Two ways to solve this: First is to check what network docker-compose created for your elasticsearch setting (docker network ls) and then run your DW app with

docker run --network= ...

Second way is to create a network docker network create elastic and use it as external network in your docker compose file as well as in your docker run command for the DW app.

Docker compose file could then look like

Your approach is generally a good approach. You can add checking not necessarily for the timestamp of creation time, but whether the image is actually the one that you previously built (someone else may have built a newer image with a different contents that may not reflect your repository anymore).

In general make decides whether to make a target or not by comparing timestamps of dependencies, so they are most commonly files. The list of dependencies may be manipulated however with some logic, which allows you to run arbitrary checks.

In your scenario you already store the image ID in a file. This may now be used to check whether the current image ID is the same that we built previously. We may compare output of the same command (extracted to a variable for DRY-ness) with the stored contents upon dependencies evaluation; if they do not match, we issue dependency of FORCE which is .PHONY and therefore always out of date, effectively triggering target remake:

You can't do this at build time. A container's max disk space can be only limited at runtime.

Now, if you are concerned that your disk might get full due to Docker stuff (images, logs, etc), what you can do is mount /var/lib/docker in a partition different than the main system partition, this way you know that getting out of space in docker won't crash your system. Or in case of Docker for Mac, you have a disk limit in the preferences.

file/to/be/copied just lies in Folder, so you just need to set this folder as build context, like next:

As it is .net Core, which is open source, have you looked up the sources at github. There you'lkl find a call to the CrlCache which shows where data is stored:

I don't think it's currently possible. If you check gitlab's permissions model, you'll see that the user access levels determine what you can do in the container registry:

• read rights are available as Reporter+
• update rights are available as Developer+

If your users are developers, then they will be able to push images to the registry. If you want to limit that to gitlab-ci builds, you'd need to use protected branches and limit your users to Reporter access level (probably not what you want).

An alternative a bit convoluted would be to setup a second project that is used as the source for images, and configure its build setup to pull from the first project protected branch. Commits to the protected branch in the first project would always have to be reviewed and docker images would be pulled from the second project.

in your pipeline you are doing two times (master and staging)git checkout in same directory i.e. workspace directory. So final result will be checkout of staging directory.

You can simplify the build process by creating two jobs one is for production and one is for staging, don't mix both in one job.

Below example is for staging:

On your build args you are passing SERVER_TYPE and referencing $SYSTEM_TYPE on your dockerfile, that should fix it!

You must publish the port at runtime like this: docker run -p 8000:8000 image-id.