docker-compose - resolving hostname about cloud-builders-community HOT 2 OPEN

I'm also seeing closed #90, but that doesn't really help this current situation (the linked examples just show the host and port resolving to container_name and the external port in the compose configuration).

from cloud-builders-community.

Ah, so a couple of crucial observations here:

1. It is indeed container_name; but it's the internal port (which means mapping the port to the docker host is superfluous).

2. It's different for gcr.io/cloud-builders/docker steps because (speculating) GCB is doing less under-the-hood. In a docker run step, you can get in with --network=cloudbuild (and port is still internal).

Example docker-compose.yml:

version: '3.4'
services:
  web-server:
    image: nginx
    container_name: web-server
networks:
  default:
    external:
      name: cloudbuild

and cloudbuild.yml with wget:

steps:
- name: 'docker/compose:1.22.0'
  args: ['up', '-d']
- name: 'gcr.io/cloud-builders/wget'
  args: ['http://web-server:80']

and cloudbuild.yml with docker run:

steps:
- name: 'docker/compose:1.22.0'
  args: ['up', '-d']
- name: 'gcr.io/cloud-builders/docker'
  args: ['run', '--network=cloudbuild', 'byrnedo/alpine-curl', 'http://web-server:80']

Before closing this: does that all smell correct, or am I missing something?

from cloud-builders-community.