Skip to content

Make fails with make: *** [binary] Error 1 #94

Closed

Description

@dave-tucker

Make fails with the helpful error message of make: *** [binary] Error 1

A little debugging shows that https://github.com/docker/cli/blob/master/scripts/build/.variables#L7 is the issue.

On OSX:

$ date --utc --rfc-3339 ns
date: illegal option -- -
usage: date [-jnRu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
            [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]

I know that the README now shows the Dockerized make targets so this will only be an issue for people like me on OSX who didnt RTFM 😁

I guess it would be nice to be fixed or for the dockerized makefile to be the default one.

Activity

  1. thaJeztah commented on May 16, 2017

    @thaJeztah
    Member

    What exact command did you run? make binary or just make ?

  2. dave-tucker commented on May 16, 2017

    @dave-tucker
    ContributorAuthor

    just make

  3. dnephin commented on May 16, 2017

    @dnephin
    Contributor

    I believe I fixed this in #78 , are you on latest master?

    Edit: actually I fixed it for alpine, but not for "host" development. I dont' think we can support developing on the host.

    Make fails with the helpful error message of make: *** [binary] Error 1

    This is unfortunate, but that's how bash decides to error out on undefined variables with set -u.

  4. dnephin commented on May 16, 2017

    @dnephin
    Contributor

    I guess it would be nice to be fixed or for the dockerized makefile to be the default one.

    This was discussed in #78 as well: #78 (comment)

    I think we'll look at replacing docker.Makefile with a ./build.sh for now

  5. dave-tucker commented on May 16, 2017

    @dave-tucker
    ContributorAuthor

    Yes I'm on latest master. Both make and make binary insta-fail on OSX.

  6. thaJeztah commented on May 16, 2017

    @thaJeztah
    Member

    Oh, 🤦 this is the docker/cli repo, ignore me

  7. dnephin commented on May 16, 2017

    @dnephin
    Contributor

    We could also add a check to the Makefile that warns if it's not being run from an expected environment. Maybe docker.Makefile (and the future ./build.sh) could set DOCKER_CLI_THIS_IS_FINE=1. Anyone who has setup their host can export that as well to remove the warning.

    Then in Makefile if the environment variable isn't set we can warn "you probably want ./build.sh"

  8. dnephin commented on Jun 1, 2017

    @dnephin
    Contributor

    This has been partially fixed by removing the "develop on the host" instructions from the README. We also have #99 to track other related improvements. #107 introduces the script I suggested here.

    Going to close this issue since we have another tracking issue.

  9. added a commit that references this issue on Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions