Get outbound IP in multiple ways or disable cache server if failed to init #74

Merged
wolfogre merged 1 commits from bugfix/get_outbound_ip into main 2023-03-24 09:55:13 +00:00
wolfogre commented 2023-03-24 08:53:22 +00:00 (Migrated from gitea.com)

Fix #64 (incompletely).

It's still not ideal. It makes more sense to use the gateway IP address of container network as outbound IP of cache server. However, this requires act to cooperate, some think like:

  • act creates the network for new container, and returns the network to runner.
  • runner extracts the gateway IP in the network.
  • runner uses the gateway IP as outbound IP, and pass it to act as cache server endpoint.
  • act It continues to create the container with the created network.
Fix #64 (incompletely). It's still not ideal. It makes more sense to use the gateway IP address of container network as outbound IP of cache server. However, this requires act to cooperate, some think like: - act creates the network for new container, and returns the network to runner. - runner extracts the gateway IP in the network. - runner uses the gateway IP as outbound IP, and pass it to act as cache server endpoint. - act It continues to create the container with the created network.
lunny (Migrated from gitea.com) approved these changes 2023-03-24 09:46:44 +00:00
Sign in to join this conversation.