Once we've determined which containers we plan on building, we need a sensible directory hierarchy so that its easier for scripts to find what dockerfiles are needed.

Comments

Mixologic created an issue. See original summary.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Parent issue: » #2840571: Container Build process improvements
Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented

The build process should probably use git to get at its dockerfiles, so that a build can use a URL instead of a directory

docker build -t drupalci/php-5.6-apache:testing git://git.drupal.org/project/drupalci_environments.git#2609560-Base-DCI-containers-off-official-containers:web/web-5.6

Is an example of where it uses the (old) dir structure of web/web-5.6

docker build -t drupalci/php-5.6-apache:dev git://git.drupal.org/project/drupalci_environments.git#dev:php/5.6

could be a solution...

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Status: Active » Needs work
Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented

The repo is organized now, with the root directory being either php or db. (misc soon).

The current state is that we manually maintain each docker file.

The future state is using m4 to create macros/templates of the dockerfiles (#2841923: Use m4 and make to generate the dockerfiles, because we *do not* want to use the FROM tag to reference other docker containers within the repository, because then we cannot have dev/production containers.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.