Related to #184
Add command flag of network for exec, the default value of --network is empty string. Valid values are: host , bridge, <custom_network> and empty string.
Related to #184
Add command flag of `network` for `exec`, the default value of `--network` is empty string. Valid values are: `host `, `bridge`, `<custom_network>` and empty string.
@a1012112796 , What is your host when connect to pgsql? Host should be <service-id>
In my test, can be access to service container:
@a1012112796 , What is your host when connect to pgsql? Host should be `<service-id>`
In my test, can be access to service container:
@a1012112796 , What is your host when connect to pgsql? Host should be <service-id>
In my test, can be access to service container:
oh, I see, In actions defined in gitea repo, It has add a special config
after remove it, it works.
by the way, this change will hhave other error in github, I wondoer why the result is different...
/cc @techknowlogick
> @a1012112796 , What is your host when connect to pgsql? Host should be `<service-id>`
> In my test, can be access to service container:
> 
oh, I see, In actions defined in gitea repo, It has add a special config
after remove it, it works.
by the way, this change will hhave other error in github, I wondoer why the result is different...
/cc @techknowlogick
@a1012112796 Hi, The actions of Gitea on GH should run a job directly on the runner machine. So you need to append this record to the /etc/hosts. as you can see, we must map the ports on the service container to ports on the Docker host in this mode.
But for Gitea Actions, each job is executed inside docker container by default. And act_runner will created a new docker network for job container and its service containers. All these containers will connect to this network, and we use <service-id> as an alias when service container connect to the network. So we can be access to the service containers by <service-id>:<port> in the steps of job.
> I wondoer why the result is different...
@a1012112796 Hi, The actions of Gitea on GH should run a job directly on the runner machine. So you need to append this record to the `/etc/hosts`. as you can see, we must map the ports on the service container to ports on the Docker host in this mode.
But for `Gitea Actions`, each job is executed inside docker container by default. And `act_runner` will created a new docker network for job container and its service containers. All these containers will connect to this network, and we use `<service-id>` as an alias when service container connect to the network. So we can be access to the service containers by `<service-id>:<port>` in the steps of job.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Related to #184
Add command flag of
networkforexec, the default value of--networkis empty string. Valid values are:host,bridge,<custom_network>and empty string.sadly, still can't connect to
services.@a1012112796 , What is your host when connect to pgsql? Host should be
<service-id>In my test, can be access to service container:
oh, I see, In actions defined in gitea repo, It has add a special config
after remove it, it works.
by the way, this change will hhave other error in github, I wondoer why the result is different...
/cc @techknowlogick
@a1012112796 Hi, The actions of Gitea on GH should run a job directly on the runner machine. So you need to append this record to the
/etc/hosts. as you can see, we must map the ports on the service container to ports on the Docker host in this mode.But for
Gitea Actions, each job is executed inside docker container by default. Andact_runnerwill created a new docker network for job container and its service containers. All these containers will connect to this network, and we use<service-id>as an alias when service container connect to the network. So we can be access to the service containers by<service-id>:<port>in the steps of job.