1. The`setup` block will run and preload data or setup any custom commands you have placed in the property

1. The actual pipeline step will now run with the service container attached in the same network.

Ideally, your application should be able to access other services by other DNS names that are fully configurable (this is a very good practice for[integration tests]({{site.baseurl}}/docs/docs/testing/integration-tests/) as well).

Sometimes, however, and especially in legacy applications, your application might be hardcoded to look at other services at “localhost”

In that case, you can use the attribute`shared_host_network: true` on the services definition. Now all linked containers can access each other's services via localhost. Here is an example:

version: "1.0"

steps:

my_first_step:

image: goodsmileduck/redis-cli

title: Storing Redis data

commands:

- apk add curl

- redis-cli -u redis://localhost:6379 -n 0 LPUSH mylist "hello world"

- curlhttp://localhost:80

- echo finished

services:

shared_host_network: true

composition:

my_redis_service:

image: 'redis:latest'

You can also do the same thing with top level services:

version: "1.0"

services:

name: my_database

shared_host_network: true

composition:

my_redis_service:

image: 'redis:latest'

my_nginx:

image: 'nginx'

steps:

my_first_step:

image: goodsmileduck/redis-cli

title: Storing Redis data

commands:

- apk add curl

- redis-cli -u redis://localhost:6379 -n 0 LPUSH mylist "hello world"

- curlhttp://localhost:80

- echo finished

services:

- my_database

Note: we do recommend you only use this option as a last resort. You should not hardcode “localhost” as a requirement in your services.

Service containers are not compatible with[custom pipeline steps]({{site.baseurl}}/docs/codefresh-yaml/steps/#limitations-of-custom-plugins).

- Accessing Containers via localhost -[documentation]({{site.baseurl}}/docs/codefresh-yaml/service-containers/)

- The[Modified Files filter]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/git-triggers/#monorepo-support-modified-files) will now work on triggers triggered by Pull Request events. Notice: this might cause unexpected behavior if you have a trigger that is triggered by both Pull Request and Commit events with a Modified Files filter set. Previously the Modified Files filter would be ignored for Pull Request events. If you need different filters for Pull Requests and Commit events, we recommend you separate the trigger.

- Codefresh Runner on Rancher RKE 2.X -[documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#installing-on-rancher-rke-2x)