Farcaster Devs

Has anyone tried running `yarn identity create` on the Hub docker image?

I am getting the attached error.

I'd love for it to create the identity, then i'll start the hub.

If I run the dockerfile directly the identity is missing.

Has any of you tried running Hubs on Kuberentes? or y'all on ECS? @manan @sds @sanjay 

Github: HEAVY WIP Code (link will be gone once merged)

Building @warpcast and @farcaster. Previously Coinbase, Brigade, Causes.

🪐 Building @neynar, join us in /neynar

Developer 🤓 build, develop and operate Farcaster solutions @ dtech.vision also love tech, decentralization, fitness and oldschool rap 😎

Has any of you tried running Hubs on Kuberentes? or y'all on ECS? @manan @sds @sanjay 

Github: HEAVY WIP Code (link will be gone once merged)
https://github.com/dtechvision/onchain-helmcharts/blob/leewardbound-patch-1/farcaster/hubs/values-example.yaml

In case it helps, in the container everything is empy besides /home/node/app and there yarn install fails

cc @leewardbound thanks for the idea to try building in the docker itself again (I assumed Dockerfile already copies that)

Full-stack digital product consultant @ BoundCorp.net - Regenfrogs.xyz - goldmongers.xyz - Reno NV

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

thank you so much for the detailled answer! 

then running yarn identity create is likely different to running it directly in the docker image for you?

I am trying to go from no setup to having a running hub in K8s

Goal:

Helm Chart deploys an init container or script to run yarn create identity if it's the first time running. If not start directly with npx pm2-runtime ... like in the docker compose

I oriented myself on the docker-compose but can't get yarn identity create to work as outlined above.

Seems like only /home/node/app has files (node_modules, packages, package.json) while /home/node/app/apps/hubble as directory exists but is completly empty

yarn install  in the /home/node/app dir fails with 

[4/5] Linking dependencies...
[5/5] Building fresh packages...
success Saved lockfile.
$ patch-package
/bin/sh: 1: patch-package: not found
error Command failed with exit code 127.
node@hubble-main-7ccd664cbc-bgznk:~/app$ 

Dockerfile: 1.15.0 and 1.14.5 both

We currently run hubs on AWS Fargate (ECS). We are going to migrate to running on EC2 instances soon.

Primary reasons (high level):

- Hubs in general have a "pet" instead of a "cattle"-like design in that the gossip protocol requires the node to have a reasonable static/stable IP. I'd love for us to move more towards cattle, but it's not a priority.

- Fargate doesn't support static/stable IPs unless you use an NLB, and AWS' NLBs cause issues (CC @cassie)

- ECS as a platform doesn't give you as much access to what happening on the underlying instance (understandably)

- Where you serve read/writes for hub storage has a significant impact on performance, so making use of attached storage (e.g. instance store volumes)

Since the hub can always re-sync with the network if you lose the node, loss of data during instance failure is fine for our use case.