le-docker | Logentries/Docker integration examples | Continuous Deployment library

I'm trying to set up a docker-compose definition, where I have a mongoDB container, and a nodeJS container that connects to it.

Disclaimer: I aware the /var/run/docker.sock issue is way common and there are lots of posts out there on it (although most if not all can be summed up to adding the running user to the docker permissions group). I tried all the those instructions and it still does not help me, in redhat.

I have two containers, one Ubuntu and one running Redhat 7.9. My problem is specifically not being able to run - in the redhat container only - a call to Docker.Dotnet's ListImages (fails with permission denied in /var/run/docker.sock). In the beginning, I was not able to issue any docker command without prefixing it with sudo. I then added the running user to the docker permissions group, and can issue docker commands without sudo. But Docker.Dotnet ListImages (which is simply a wrapper to docker api's images/json endpoint) still fails with the permission denied error on docker.sock. I tried all recommended here, to no avail.

I thought perhaps I should add the User=root (although this is not present in my Ubuntu service file, and therefore does not make much sense). I then realized that the ubuntu and redhat docker service files differ considerably.

Ubuntu:

I have created a Node application for which I want to automate the deployment. Up till now I only automated the building process, i.e. install dependencies, create the docker image and push to the Azure Container Registry. This works perfectly fine and corresponds to the code below which is not commented away. In the current process I still need to

1. manually change the image tag in my helmfile configuration and
2. manually perform a helmfile -environment= sync.

My struggle is in the second part, for I believe the first part is easily implemented when I have a setup for the second.

In the source directory of the repository I have the helmfile.yaml which could be called immediately after the build. This is what I tried to achieve with the below setup which is commented. My thoughts were to have a container on which helfmile is already installed, e.g. cablespaghetti/helmfile-docker, then connect to the K8s cluster using the Azure kubectl task to do so, followed by executing the helmfile sync command. This approach failed as I got a Docker exec fail with exit code 1, probably because the specified container uses the ENTRYPOINT approach, which is not allowed in the Azure Pipeline.

The approach however feels somewhat cumbersome, as if I am missing a much simpler approach to 'simply' perform a helmfile sync command. How can I get this to work?

I am quite new to docker technology and still learning and reading through the docs. I have an oracle base image which i would like to use as a parent image to build my own image and then pushing it towards custom docker registry/repository.

The base image already provides a full setup of oracle db. But as next steps, i would like

• download a dump file (e.g. dump url) directly into the docker image (without downloading to local workspace)
• run some sql script
• lastly, import the dump using data pump (impdp)

I tried to follow https://github.com/mpern/oracle-docker, but here you always need to store dump file locally and point it as volume.

Is it possible if i can use curl command to download and directly store in oracle docker container workspace? Afterwards importing it from there

I'm trying to optimize build time in my azure devops pipeline, but the npm install stage in my dockerfile just will not cache. Why?

This is my dockerfile. I've separated copying the package*.json files and npm install into it's own layer before copying the rest of my sources, as this is best practice and should make the npm install layer be cacheable between builds.

I would like to access the Docker API (running on Windows Server). Sadly a TCP connection is not possible in our network (at least for this case).

Here I found a solution to change the port. But I am not sure if changing the protocol is possible?

Is there any other ansible-docker module to capture all the containers on the VM even the ones in exited status.

I have added a .gitlab-ci.yml to my private project. One of the steps is to get a role from a private gitlab repo. However this fails with

We use a Docker image to run CI builds. The Docker image has a system-installed Ruby. The Docker container has the content of gem env and bundle env as indicated in the gist linked files: