Anvil and foundry on separate hosts ?

[danielaugot]

Hi everyone

I want to design a university lab, where I run anvil on some lab machine, and students interacts with the foundry client on their computer. I am struggling with that. I have an anvil machine and a foundry (actually networked containers). I get

root@anvil:/anvil# cast block-number 
23291554

but

root@foundry:/foundry# cast block-number --rpc-url http://anvil:8545/rpc
Error: HTTP error 404 with empty body

At least, it's a start, foundry can talk to anvil and find an HTTP server. But how do I get proper answers?
Daniel

[zerosnacks]

Hi Daniel, have you tried using anvil --host 0.0.0.0?

[danielaugot]

Thanks for the suggestion. I tried and still get the same 404 message. My container is set in docker-compose.yaml as follow

  anvil:
    image: foundry
    container_name: anvil
    environment:
      ANVIL_IP_ADDR: "0.0.0.0"
    working_dir: /anvil
    ports:
      - "8545:8545"
    hostname: anvil
#    command: anvil
    command: tail -f /dev/null

I then get a shell on it and start anvil manually. Could that be a docker issue?

[zerosnacks]

I think you will need to have a network in your Docker compose your other containers can connect to or further expose it with a reverse proxy

[danielaugot]

Hi, docker-compose gracefully makes a network for me

augot@chichille: ~/05-foundry$ docker-compose  up
[+] Running 3/3
 ✔ Network 05-foundry_default  Created                                     0.0s 
 ✔ Container foundry           Created                                     0.1s 
 ✔ Container anvil             Created     

and my containers are connected

root@foundry:/foundry# ping anvil
PING anvil.dns.podman (10.89.1.4): 56 data bytes
64 bytes from 10.89.1.4: icmp_seq=0 ttl=153 time=0.052 ms

and

root@anvil:/anvil# ping foundry
PING foundry.dns.podman (10.89.1.5): 56 data bytes
64 bytes from 10.89.1.5: icmp_seq=0 ttl=159 time=0.016 ms

[danielaugot]

Do I really need to install reverse proxy?

[danielaugot]

Hi! Thanks for the suggestion. I tried it, but I get the same 404 error.