`tesseract serve --network host` does not work as expected

[andrinr]

Description

Currently, higher order tessseracts don't work when used with built images because of networking issues. The only way to make it work is by having one tesseract on another machine or by using from_tesseract_api on the HOT instance.

Steps to reproduce

A reproducer can be found here:

https://github.com/pasteurlabs/tesseract-core/blob/main/demo/_showcase/ansys-shapeopt/optimization_os.ipynb.

if we replace

design_tess = Tesseract.from_tesseract_api("sdf_fd/tesseract_api.py")

with

sdf_fd_tess = Tesseract.from_image("sdf_fd")
sdf_fd_tess .serve()

we get a connection error.
I have tried setting

sdf_fd_tess = Tesseract.from_image("sdf_fd", network="host")
sdf_fd_tess .serve()

but without sucess.

Logs

OS

Linux

Tesseract version

1.1.1

[dionhaefner]

Thanks for the report. Is this example working on your machine? This should be covered by CI so I'd be surprised to find it broken.

[andrinr]

I have not tried this specific configuration, probably this will work!

[andrinr]

That works :)

[dionhaefner]

@zmheiko Could you confirm whether this is expected behavior or not? Should network="host" work?

[zmheiko]

@linusseelinger had problems with network="host" and docker a while ago. Interestingly everything worked just fine using colima, which is probably why I never had issues with it before. We concluded that it's likely a docker on Mac related issue. Are you running on Mac?

[andrinr]

@dionhaefner network="host" did not work for me. What I tried is:

1. setup the network
   docker network create my_network

2. Serve the tesseract from the CLI, read out the network IP and port numberfrom the echo:
   tesseract serve "geo_airfoil:latest" --network my_network --network-alias helloworld

note that the python tesseeract api is not very usable here as when I run:

 geo_tess = Tesseract.from_image("geo_airfoil",  network="my_network", network_alias="geo_airfoil")
geo_tess.serve()

I cannot obtain the network url and the port number. I will have to manually get those.

3. Access the lower Tesseract from the HOT using Tesseract.from_url with the infos obtained from the previous step. Using the network IP adress alias does not work with Tesseract.from_url.

However unlike I stated before, this does currently NOT work for me, however I am not a 100% sure if there is something wrong with the data I am sending or if the issue is somewhere else.

[dionhaefner]

OK I'm getting confused. @andrinr does this work for you or not?

docker network create my_network
tesseract serve "helloworld:latest" --network my_network --network-alias helloworld
tesseract run "multi-helloworld:latest" apply '{"inputs": {"helloworld_tesseract_url": "http://helloworld:8000" , "name": "YOU"}}' --network my_network

[zmheiko]

@dionhaefner this works for me but only if I add --port 8000 to the serve command. Otherwise the port is assigned randomly I think. This seems to be a mistake in the example doc. Does that fix the issue @andrinr ?

[andrinr]

That one does work! Sorry for the confusion then!