Relative build.yml and Dockerfile paths not generating the Dockerfile.generated at the right location about habitus HOT 6 CLOSED

thanks for the bug report @chdeliens
i will take a look as soon as possible (need to upgrade the docker client lib anyways soon)

from habitus.

@chdeliens I found the issue with your example, because your build.yml is in the builder directory you need to change your build.yml to the following example and it works:

build:
  version: 2016-03-14
  steps:
    builder:
      name: builder
      dockerfile: Dockerfile

-f is telling to use builder/build.yml but you at the moment it's using /builder as the reference, you don't need to prefix the Dockerfile with the /builder directory.

from habitus.

Related issue, not sure if it should be a new issue.

Wanted to have individual Dockerfiles exist in their own subdirectories, so they could all keep the name "Dockerfile" rather than be "Dockerfile.something". This allows for syntax highlighting of the Dockerfiles in editors like PyCharm and Sublime Text.

However, if I have the following directory structure:

.
├── build.yml
├── mf_builder
│   ├── Dockerfile
│   └── Dockerfile.generated
├── run.sh
├── scripts
│   ├── cloneRepos.sh
│   ├── installruby.sh
│   ├── installruby_docker.sh.bak
│   └── ucplayer_build.py
└── ucplayer_builder
└── Dockerfile

And build.yml:

build:
  version: 2016-03-14 # version of the build schema.
  steps:
    mf_builder:
      name: mf_builder
      dockerfile: mf_builder/Dockerfile
    ucplayer_builder:
      name: ucplayer_builder
      dockerfile: ucplayer_builder/Dockerfile
      depends_on:
        - mf_builder
      secrets:
        id_rsa:
          type: file
          value: _env(HOME)/.ssh/id_rsa

I end up with an issue similar to @chdeliens.

2017/03/24 14:42:07 ▶ Collecting artifact information
2017/03/24 14:42:07 ▶ Building 2 steps
2017/03/24 14:42:07 ▶ Step 0 - mf_builder: mf_builder
2017/03/24 14:42:07 ▶ Step 1 - ucplayer_builder: ucplayer_builder
2017/03/24 14:42:07 ▶ Parallel build for mf_builder
2017/03/24 14:42:07 ▶ Building mf_builder
2017/03/24 14:42:07 ▶ Parsing and converting 'mf_builder/Dockerfile'
2017/03/24 14:42:07 ▶ Starting API on 8080
2017/03/24 14:42:07 ▶ Writing the new Dockerfile into mf_builder/Dockerfile.generated
2017/03/24 14:42:07 ▶ Building the mf_builder image from Dockerfile.generated
2017/03/24 14:42:07 ▶ Build for step mf_builder failed due to API error (500): {"message":"Cannot locate specified Dockerfile: Dockerfile.generated"}

Was wondering if Habitus can already support this directory structure, perhaps with some changes to the build.yml or having separate build.yml files with each Dockerfile, or if I must stick with one build.yml in the same directory as all Dockerfiles.

from habitus.

I second the previous poster's request. Please reopen this issue.

I have complex Dockerfiles each in it's own directory.

Will Habitus support that anytime soon?

from habitus.

Hi @GertThiel,

I did some work on the next release to fix this issue. Can you try your example with the pre-release please. You can download the pre-release here: https://github.com/cloud66/habitus/releases/tag/0.4.11_pre

Please let me know.

Daniël,

from habitus.

That helped @kamerblauwlicht. Thanks a lot.

from habitus.