ff start <stackname> results in error - 'Could not create the account: account already exists'

[rakshita-kaulgud]

firefly % ff start trial --verbose
reading stack config... done
this will take a few seconds longer since this is the first time you're running this stack...
starting FireFly stack 'trial'... initializing blockchain node
/usr/local/bin/docker-compose down --volumes
trial Warning: No resource found to remove
Error: docker run --rm -v /Users/kaulgudramer/.firefly/stacks/trial/blockchain:/geth -v trial_geth:/data ethereum/client-go:release-1.9 --nousb account import --password /geth/password --keystore /data/keystore /geth/0/keyfile
Failed [1] INFO [10-01|19:15:54.069] Maximum peer count ETH=50 LES=0 total=50
INFO [10-01|19:15:54.069] Smartcard socket not found, disabling err="stat /run/pcscd/pcscd.comm: no such file or directory"
INFO [10-01|19:15:54.070] Set global gas cap cap=25000000
Fatal: Could not create the account: account already exists
Fatal: Could not create the account: account already exists

• all changes rolled back
  Usage:
  ff start <stack_name> [flags]

Flags:
-h, --help help for start
-n, --no-pull Do not pull latest images when starting
-b, --no-rollback Do not automatically rollback changes if first time setup fails

Global Flags:
--ansi string control when to print ANSI control characters ("never"|"always"|"auto") (default "auto") (default "auto")
-v, --verbose verbose log output

Error: docker run --rm -v /Users/kaulgudramer/.firefly/stacks/trial/blockchain:/geth -v trial_geth:/data ethereum/client-go:release-1.9 --nousb account import --password /geth/password --keystore /data/keystore /geth/0/keyfile
Failed [1] INFO [10-01|19:15:54.069] Maximum peer count ETH=50 LES=0 total=50
INFO [10-01|19:15:54.069] Smartcard socket not found, disabling err="stat /run/pcscd/pcscd.comm: no such file or directory"
INFO [10-01|19:15:54.070] Set global gas cap cap=25000000
Fatal: Could not create the account: account already exists
Fatal: Could not create the account: account already exists

• all changes rolled back

[nguyer]

After some investigation, I believe this issue is a symptom of #106 and named volumes from a previously failed start not getting cleaned up correctly. Since fixing #106 I haven't seen this issue anymore. @rakshita-kaulgud can you please test with the latest CLI (v0.0.33) and report back if you're still seeing this?

[rakshita-kaulgud]

@nguyer With the latest changes, this issue seems to be fixed on a machine with docker-compose v2.0.0.