Error when using mutagen compose up: unable to bring up Mutagen service: up command failed: exit status 1

[Stefdewa]

Which version of Mutagen are you using (mutagen version)?

v0.12.0-beta2

Which operating system (platform/version/architecture) are you using?

Running Windows 10 Pro with docker-for-windows 2.2.0.5.

Detailed Windows specs:

OS Name	Microsoft Windows 10 Pro
Version	10.0.19042 Build 19042
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	STEF-PC
System Manufacturer	Dell Inc.
System Model	Dell Precision M3800
System Type	x64-based PC
System SKU	Dell Precision M3800
Processor	Intel(R) Core(TM) i7-4702HQ CPU @ 2.20GHz, 2201 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date	Dell Inc. A06, 16/07/2014
SMBIOS Version	2.7
Embedded Controller Version	0.06
BIOS Mode	UEFI
BaseBoard Manufacturer	Dell Inc.
BaseBoard Product	Dell Precision M3800
BaseBoard Version	A06
Platform Role	Mobile
Secure Boot State	On
PCR7 Configuration	Elevation Required to View
Windows Directory	C:\WINDOWS
System Directory	C:\WINDOWS\system32
Boot Device	\Device\HarddiskVolume3
Locale	Belgium
Hardware Abstraction Layer	Version = "10.0.19041.488"
Username	stef-pc\Stef
Time Zone	Romance Standard Time
Installed Physical Memory (RAM)	16,0 GB
Total Physical Memory	15,9 GB
Available Physical Memory	4,95 GB
Total Virtual Memory	30,4 GB
Available Virtual Memory	16,6 GB
Page File Space	14,5 GB
Page File	C:\pagefile.sys
Kernel DMA Protection	Off
Virtualisation-based security	Running
Virtualisation-based security required security properties	
Virtualisation-based security available security properties	Base Virtualisation Support, Secure Boot, DMA Protection
Virtualisation-based security services configured	
Virtualisation-based security services running	
Device Encryption Support	Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.	

What is the issue that you're experiencing?

When performing a mutagen compose up -d I get the docker-compose help output and an error message unable to bring up Mutagen service: up command failed: exit status 1

What are the steps to reproduce the issue?

Setup docker-compose.yml:

version: '2.3'
services:
  www:
    image: nginx:1.16
    restart: unless-stopped
    mem_limit: 64m
    memswap_limit: 64m
    ports:
    - "80"
    networks:
    - default
    volumes:
    - code:/var/www/html

volumes:
  code:

x-mutagen:
  sync:
    defaults:
      ignore:
        vcs: true
    code:
      alpha: /c/lokal.host/projects/test/repo # local file system
      beta: "volume://code" # container file system.
      mode: "two-way-resolved"
      ignore:
        paths: # Ignore these when syncing.
          - "*/node_modules/*"
          - "vendor/*"
      configurationBeta:
        permissions:
          defaultFileMode: 0666
          defaultDirectoryMode: 0777

What is the expected result of these steps in the absence of the issue?

Start mutagen sync and start containers.

What is the actual result?

Output of mutagen compose up -d

Define and run multi-container applications with Docker.
Usage:
  docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]
  docker-compose -h|--help
Options:
  -f, --file FILE             Specify an alternate compose file
                              (default: docker-compose.yml)
  -p, --project-name NAME     Specify an alternate project name
                              (default: directory name)
  --verbose                   Show more output
  --log-level LEVEL           Set log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)
  --no-ansi                   Do not print ANSI control characters
  -v, --version               Print version and exit
  -H, --host HOST             Daemon socket to connect to
  --tls                       Use TLS; implied by --tlsverify
  --tlscacert CA_PATH         Trust certs signed only by this CA
  --tlscert CLIENT_CERT_PATH  Path to TLS certificate file
  --tlskey TLS_KEY_PATH       Path to TLS key file
  --tlsverify                 Use TLS and verify the remote
  --skip-hostname-check       Don't check the daemon's hostname against the
                              name specified in the client certificate
  --project-directory PATH    Specify an alternate working directory
                              (default: the path of the Compose file)
  --compatibility             If set, Compose will attempt to convert keys
                              in v3 files to their non-Swarm equivalent
Commands:
  build              Build or rebuild services
  bundle             Generate a Docker bundle from the Compose file
  config             Validate and view the Compose file
  create             Create services
  down               Stop and remove containers, networks, images, and volumes
  events             Receive real time events from containers
  exec               Execute a command in a running container
  help               Get help on a command
  images             List images
  kill               Kill containers
  logs               View output from containers
  pause              Pause services
  port               Print the public port for a port binding
  ps                 List containers
  pull               Pull service images
  push               Push service images
  restart            Restart services
  rm                 Remove stopped containers
  run                Run a one-off command
  scale              Set number of containers for a service
  start              Start services
  stop               Stop services
  top                Display the running processes
  unpause            Unpause services
  up                 Create and start containers
  version            Show the Docker-Compose version information
Error: unable to bring up Mutagen service: up command failed: exit status 1

Is there any other information that might be helpful?

Another windows user with the same project (docker-compose.yml) and the same versions (Windows, Docker and Mutagen) doesn't have this issue. So it must be something specific for this machine.

I looked at the codebase for release v0.12.0-beta2. The error is throw in the mutagen codebase at cmd/mutagen/compose/up.go line 279. It stems from function ensureMutagenUp from the same file line 32.

EDIT

Forgot to mention, creating a mutagen sync manually using the instruction from #235 works. Not expecting a solution on a silver plate here but a direction to figure out what is wrong of a log/error file with more info would help greatly to find the problem. Thanks for the good work!

[CaliGlenn]

I have exactly the same problem with more or less the same specs!

[jordanmiguel]

up?

[xenoscopic]

It's probably a little too late to debug this now (sorry), but this was very likely due to Mutagen's imperfect Compose V1 emulation. Support for Compose V1 has now been dropped since it was a little too flakey. The path going forward is going to be the Compose-V2-based Mutagen Compose.