docker-config | Docker configuration files for my local development | Continuous Deployment library

The build step is triggered only if there is change on Dockerfile-pentaho.

The run step needs to run everytime, if the build step was triggered I want to get the image with CI_PIPELINE_ID tag, if not I want to run it with the latest tag.

I need to run the step "run" with the script below if the build step is triggered:

• docker run --rm $PENTAHO_IMAGE:$CI_PIPELINE_ID --v files/pentaho/reps/:/pentaho-di/repo/

And if not I Need to run the script below:

• docker run --rm $PENTAHO_IMAGE:latest --v files/pentaho/reps/:/pentaho-di/repo/

I've tried to create a file with touch $CI_PROJECT_DIR/success on build step and check if it exists on run step, but I can't get it to work.

here's my gitlab-ci.yml.

I am not able to connect a dockerized Spring Boot API managed by Kubernetes via Docker Desktop (Windows) to a local instance of Postgres. Error is as follows:

...

I want to execute a command using ansible 2.9.10 in remote machine, first I tried like this:

I have set up a server to host multiple websites according to this tutorial: https://blog.ssdnodes.com/blog/host-multiple-ssl-websites-docker-nginx/

I have also configured a docker-compose.yml for wordpress like they did in example 2 in the same tutorial. But when I open the website, I get an "Error establishing a database connection" Error. I remember doing this a few months back with everything working fine, but I cant remember what I did differently.

This is the error message I receive (multiple times) after typing docker-compose up

I was trying to do a quick bootstrap to see some sample data in elasticsearch.

Here is where you do a Docker Compose to get a ES Cluster: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html

Next I needed to get logstash in place. I did that with: https://www.elastic.co/guide/en/logstash/current/docker-config.html

When I curl my host, curl localhost:9200 it gives me the sample connection string. So i can tell it is exposed. Now when I run the logstash docker file from above, i noticed that during the bootstrap code it cant connect to: localhost:9200

I was thinking that the private network created in for elastic is fine for the cluster and that i didnt need to add logstash to it. Do I have to do something different to get the default logstash to interact with the default docker?

I have been stuck on this for awhile. My host system is Debian 9. I am trying to think of what the issues might be. I know that -p 9200:9200 would couple the ports together, but 9200 has been claimed by ES, so I'm not sure how I should be handling things. I didn't see anything on the Website though which says "To link the out of the box logstash to the out of the box elasticsearch you need to do X,Y,Z"

When attempting to create a terminal to the logstash server with -it though, it is continually bootstrapping logstash and isn't giving me a terminal to see what is going on from the inside.

What Recommendations do you have?

I need to migrate an ElasticSearch/Logstash process from Windows to Docker. This process works fine in Windows (Elasticsearch and Logstash are services where Logstash reads an Oracle database to feed ElasticSearch). The problem is that when I start the Logstash container, Docker becomes unresponsive and extremely slow, for example docker ps takes one minute. It takes another minute to kill the logstash container. I'm running this on Windows 10 Pro with Docker Desktop and followed these steps.

I downloaded the two images (elasticsearch:7.5.1 and logstash:7.5.1) and started the containers with

i'm trying to get my laravel app running in ec2 with docker containers. I have two containers one of the app and then one for nginx. I have created the ec2 instance with docker-machine and i've also built the docker images successfully.

Running docker-compose up also runs successfully. If I run docker ps I see the two containers running.

So I have two containers running I would expect to go to the http://ec2-ip-addy-here.compute-1.amazonaws.com/ and see the app. My hunch is that something isn't setup on AWS side correctly, maybe the VPC? I'm a novice with AWS so I don't know what to look for. Any ideas?

I'm following this guide https://hackernoon.com/stop-deploying-laravel-manually-steal-this-docker-configuration-instead-da9ecf24cd2e

I'm also using the laradock nginx dockerfile and my own dockerfile for the app

EDIT: It could be the networks that are created with docker-compose. I say that because I just checked and the network is being prepended with the service name. When I run docker network ls I see a network called php-fpm_backend. Here's my docker-compose.yml file

I have 2 microservices: frontend with next.js and a backend with node.js from where I fetch data via REST-APIs from the frontend.

I now have the problem, that my 2 services don't seem to communicate directly to eachother, the thing is, it works when I fetch the data at the beginnning with the getinitialProps() Method with the fetch-API. My server-side frontend finds the backend via its service-name. However, when I am doing a http-request from the client to the backend (e.g via browser form inputs). It cannot find the backend anymore? Why is that?

here is my docker-compose.yml:

I am trying to get a instance of Gitlab running on a relative path (/dev/git/) behind a Traefik proxy.
Gitlab itself works like a charm, but I have no luck with adding a Runner to the project.

The registration of the runner ist successfully, but when it grabs a job, the cloning of the repository fails with a timeout error: