I am trying to start `carthagenet.sh` in RPC mode on Ubuntu 18.04

```
$ ./carthagenet.sh start --rpc-port 8732

```

It appears to start fine:

```
v7.0: Pulling from tezos/tezos
Digest: sha256:da126e8d6bf137a9b326c3992c0e464622b94e2ee42b7d311df158212b8ae153
Status: Image is up to date for tezos/tezos:v7.0
docker.io/tezos/tezos:v7.0
Creating network "carthagenet_default" with the default driver
Creating carthagenet_node_1     ... done
Creating carthagenet_upgrader_1                   ... done
Creating carthagenet_baker-006-PsCARTHA-test_1    ... done
Creating carthagenet_endorser-alpha-test_1        ... done
Creating carthagenet_endorser-006-PsCARTHA_1      ... done
Creating carthagenet_baker-006-PsCARTHA_1         ... done
Creating carthagenet_accuser-alpha_1              ... done
Creating carthagenet_accuser-006-PsCARTHA-test_1  ... done
Creating carthagenet_accuser-alpha-test_1         ... done
Creating carthagenet_endorser-006-PsCARTHA-test_1 ... done
Creating carthagenet_baker-alpha-test_1           ... done
Creating carthagenet_endorser-alpha_1             ... done
Creating carthagenet_baker-alpha_1                ... done
Creating carthagenet_accuser-006-PsCARTHA_1       ... done

```

However, as soon as I run any command I get an error:

```
$ ./carthagenet.sh client list known addresses
Error response from daemon: Container 9920d6b346868d3d5491c0cd88eee100189c470d2107fa49cde6086568ec1383 is restarting, wait until the container is running

```

I used the following command to debug issues with the docker container:

```
docker logs --tail 50 --follow --timestamps 9920d6b346868d3d5491c0cd88eee100189c470d21

```

It appears the docker container keeps trying to restart with this error message:

```
2020-05-14T07:02:29.592446544Z Current public chain: 2018-06-30T16:07:32Z.
2020-05-14T07:02:29.593149945Z Local chain data: 2018-06-30T16:07:32Z.
2020-05-14T07:02:29.593724545Z Updating the node configuration...
2020-05-14T07:02:29.666034593Z tezos-node: unknown option `--rpc-port'.
2020-05-14T07:02:29.666059993Z Usage: tezos-node config [OPTION]... [OPERATION]
2020-05-14T07:02:29.666064593Z Try `tezos-node config --help' or `tezos-node --help' for more information.

```

All documentation I find seems to suggest --rpc-port is the correct option. Where could I be having issues?
['https://tezos.stackexchange.com/questions/2514', 'https://tezos.stackexchange.com', 'https://tezos.stackexchange.com/users/4999/']
First off, never risk more than you can afford. Secondly, your funds are not stuck. If you look at your address, <https://tzstats.com/tz1WBKfsPLp94D7wscTRn8KFt9pBfEopdUYr>, everything is still there. As the operation shows, the operation backtracked so, no, nothing transfered.

Restart your trezor and try the transfer again. Remember, your tokens are stored on the chain, not in the device.
I have the exact same problem except a small amount. I transferred a small amount of XTZ from my coinbase account to simplestaking via my Trezor T. That went fine. Then a couple of days later, I tried to send the XTZ back to coinbase. The same thing happened that you described. I opened a chat with simplestaking to ask what the problem is. According to them, it is a known issue that is related to the latest Trezor connect update. They said they are working on a fix. They didn't tell me what will happen when they fix the bug. So I don't know if the transaction will eventually go through or it will just be canceled and the fee returned. My guess it will just be canceled and I will have to transfer later. The reason I was doing this small transfer of XTZ to/from coinbase was to test simplestaking to decide if I wanted to move all my XTZ there....LOL

However, whenever I plan on transferring a large amount of anything, I always first transfer a small amount to ensure it transfers as expected. This bug reinforces in me why I do this. I would rather pay a small extra fee then have an unnerving situation occur with a large amount.

Update: I went back on simplestaking a week later and the transaction was voided and the XTZ back in the wallet. However, I see they still charged the transfer 0.010 fee. I don't think they should be charging the fee with something like that. Does anyone know if this bug has been fixed yet? I don't want to try again until I hear it's fixed.