fix: run bacalhau in a separate container

[walkah]

Summary

Previously, we bundled bacalhau and lilypad in a single container for resource providers. This meant that any crash/exit from lilypad would restart both bacalhau and lilypad. This could create lots of phone-home version checks for bacalhau. This PR also:

• Adds a HEALTHCHECK to the bacalhau Dockerfile so that we can properly wait for it to boot before starting the RP
• Moves local dev solver to port 8081 (to avoid conflicts with kubo HTTP gateway on 8080)

Task/Issue reference

Closes: https://github.com/Lilypad-Tech/internal/issues/339

Test plan

• Integration tests should still run (using docker-compose.dev.yaml).
• For RPs, grab the latest docker-compose.yaml file and try to run. You should still be able to run jobs.

[bgins]

Suggested change

	log.Error().Msgf("error parsing output %s -> %s, %s", deal.ID, outputError, runOutput)
	log.Error().Msgf("error found while parsing output %s -> %s, %s", deal.ID, outputError, runOutput)

Possible edit. It's not a parsing error, but an error we found while parsing.

[walkah]

Do you have thoughts about it being ERR vs WARN?

[bgins]

Tough call. On the one hand, the possible error we know about (around the version check) is more of a warning. On the other hand, could there be other errors that aren't a warning?

I'd say let's go with the common case we know about and use WARN. If we start seeing other errors, we can revisit, but this may not matter once we have upgraded to the latest Bacalhau.

[walkah]

yeah, once we get fully over to the bacalhau http api, a lot of this code become moot. 👍

[bgins]

Wondering if we may want to update the solver SERVER_PORT to 8081 across the board for consistency. A few other places in the code that could be updated:

lilypad/pkg/options/server.go

Line 14 in fe48d8c

Port: GetDefaultServeOptionInt("SERVER_PORT", 8080), //nolint:gomnd

lilypad/docker/solver/Dockerfile

Line 25 in fe48d8c

EXPOSE 8080

lilypad/hardhat/scripts/print-l2-config.ts

Lines 40 to 41 in fe48d8c

	console.log('export SERVER_PORT=8080')
	console.log('export SERVER_URL=http://localhost:8080')

lilypad/stack

Line 237 in fe48d8c

-p 8080:8080 \

Outside of the code, we would need to update:

• Doppler solver projects
• Cloudflare tunnels

[walkah]

Wondering if we may want to update the solver SERVER_PORT to 8081 across the board for consistency.

My thinking (and I can be convinced otherwise) was that just in local dev / CI there's potential for port conflicts with kubo on 8080 but in deployments, it's running in a more isolated context. I can definitely to the other updates though!

[bgins]

Wondering if we may want to update the solver SERVER_PORT to 8081 across the board for consistency.

My thinking (and I can be convinced otherwise) was that just in local dev / CI there's potential for port conflicts with kubo on 8080 but in deployments, it's running in a more isolated context. I can definitely to the other updates though!

Yeah, that makes sense! Let's go with it.

[bgins]

Looks good! Integration tests and jobs running over here with the new setup. ✨