runner/artifactcache
Jason Song c9e076db68 Get outbound IP in multiple ways or disable cache server if failed to init (#74)
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.

Reviewed-on: https://gitea.com/gitea/act_runner/pulls/74
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
2023-03-24 17:55:13 +08:00
..
handler.go Get outbound IP in multiple ways or disable cache server if failed to init (#74) 2023-03-24 17:55:13 +08:00
model.go Support cache (#25) 2023-02-28 23:39:30 +08:00
README.md Support cache (#25) 2023-02-28 23:39:30 +08:00
storage.go Support cache (#25) 2023-02-28 23:39:30 +08:00
util.go Get outbound IP in multiple ways or disable cache server if failed to init (#74) 2023-03-24 17:55:13 +08:00