docker-images | Continuous Deployment library

OK, I am probably very stupid but anyways; How can I install additional pip packages via the docker-compose file of airflow?

I am assuming that their should be a standard functionality to pick up a requirements.txt or something. When inspecting their repo, I do see some ENV variables like ADDITIONAL_PYTHON_DEPS that hint me that this should be possible, but setting these in the docker-compose file doesn't actually install the library's.

I have defined the values.yaml like the following:

I've added the BitBucket server integration plugin (https://plugins.jenkins.io/atlassian-bitbucket-server-integration/) and can connect to the BitBucket cloud repo from Jenkins:

But I receive an error when I try to build:

I would like to have Prometheus and Grafana running on my developer machine using docker-images / docker-for-windows.

I have system-under-development, ASP.Net core, running on localhost:5001 and metrics are showing just fine on https://localhost:5001/metrics.

Docker-compose.yml and prometheus.yml listed below.

• If I include network_mode: host in docker-compose.yml, I can't access Prometheus on my physical machine via localhost:9090
• If I exclude network_mode and instead use ports: , I can access Prometheus on my physical machine via localhost:9090, but checking http://localhost:9090/targets, it shows https://localhost:5001/metrics as being down.

What am I doing wrong? Any comments welcome!

I'm running the Docker community edition on MacOS BigSur (11.2.2), and am trying to get into the virtual environment.

This article from 2018 says to do

$screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty

and this one from February 2020 says

$ screen ~/Library/Containers/com.docker.docker/Data/vms/0/tty

But neither of those things seem to work in my current install.

$docker --version Docker version 20.10.5, build 55c4c88

I am building a Docker image in my Azure pipeline. Now, I want to push this image to multiple aws accounts(dev, stage, prod) depending on the configuration parameters. The problem is, image is not available in publish artifact. I came across this and this article during my research. I am confused about the solution regarding saving the docker image so it can be available in publish artifact. I have two specific questions:

1. How will I use the docker save command in Azure pipeline task after docker build. The available docker task doesn't have this command.
2. Is there any better way of doing this apart from saving an image.

I'm trying to use a local image on minikube. In order to build the image I run the following command

Dockerfile:

I try to create a docker image based on Oracle Database XE.

The situation is a bit special. Oracle provides a repository that contains the scripts needed to create such an image. The images are not directly available on docker hub.

The script creates an image named oracle/database:18.4.0-xe

I use that image to copy certain files via the COPY statement. See Dockerfile.

The idea I had was to use a pre_build script to clone the oracle repository, create that image, then simply run the build on docker hub. But it seems that image is created, but not available in the build phase. That COPY statement fails as that image cannot be found.

Is there something else to do, to make that image available in the build phase?