fullnode-x deployment bugs

[insistedMarin]

1. In https://github.com/MystenLabs/sui/blob/main/docker/fullnode-x/indexer/indexer.sh

Command is missing argument --fullnode-sync-worker, so the service not work.

2. In https://github.com/MystenLabs/sui/blob/main/docker/fullnode-x/fullnode/entry.sh
   The executable file used by the instruction was created when the image was built, but was overwritten by the mounted volume when starting with the docker compose file, so it does not exist. (And due to a problem with sui-node's dockerfile, the directive was not pointing to the correct file even though the folder was not overwritten)

COPY --from=builder /sui/target/release/sui-node /opt/sui/bin/sui-node，The executable file was copied to a folder called sui-node.

3. In https://github.com/MystenLabs/sui/blob/main/docker/fullnode-x/docker-compose.yaml, There are some port conflicts.

[insistedMarin]

There is another problem. The fullnode deployed by the service does not have the rest api, but the indexer uses the rest api to obtain checkpoints.

[insistedMarin]

There is another problem. The fullnode deployed by the service does not have the rest api, but the indexer uses the rest api to obtain checkpoints.

The problem is that fullnode's config file is missing

enable-index-processing: true
enable-experimental-rest-api: true

, maybe this should be added to the documentation.

[stefan-mysten]

@johnjmartin can we check if we have these flags in the config file?