Skip to content

execute() does not work reliably in Docker containers #11076

Description

@0xEAB

I have run into this odd build failure where DUB’s build.d exits early and reports a compilation issue but no command output when using LDC v1.40.1.
I’ve been unable to reproduce this issue on my own — it only happens through build.d, not through a manual compiler invocation with the very same parameters.

Image

Even more disturbing,
the following patch seems to resolve it:

--- build.d
+++ build.d
@@ ?
- auto proc = execute(command);
+ auto proc = execute(command, null, Config(Config.Flags.stderrPassThrough | Config.Flags.inheritFDs));

Unfortunately, I cannot specify what the preconditions for triggering this are, but for me it happens within a Docker container that is about to be built.

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions