-
### Component
agent
### Describe the bug
When running woodpecker agent as follows:
`podman run -d --security-opt="label=disable" --tmpfs /tmp --cgroups=split --restart=no --label io.containers.a…
-
### Clear and concise description of the problem
As a potential user of Woodpecker I would really like to be able to provision my agent servers on an "as-needed" basis, without having to support Ku…
-
### Component
server
### Describe the bug
After migration form 0.15.11 After migration from 0.15.11 during start of server, we get this error:
```
wodpecker-server_1 | {"time":"2023-08-01T07:0…
-
### Component
server, agent
### Describe the bug
Seems like the normal clone step fails on next-101e684059 when the repo is not trusted due to the "Only inject netrc credentials into trusted …
-
repo settings -> disable `Only inject netrc credentials into trusted containers` ...
that filter is currently bit broken :/ (it does not recognice the custom clone as "trusted" one atm)
version:…
-
### Component
server
### Describe the bug
When using a local backend and specifying a `clone` configuration, the clone step fails.
This configuration:
```yaml
clone:
git:
image: plug…
-
I run a gitea server on localhost. `Skip TLS Verification` on gitea is enabled as well as `ALLOWED_HOST_LIST=external,loopback`. It is possible to do the first connection over the gitea web interface …
-
### Component
agent
### Describe the bug
Woodpecker Agent is being shown as `starting` when executing `docker ps -a` / `podman ps -a`.
### System Info
`Artix Linux Rolling - OpenRC`
``…
-
### Component
server
### Describe the bug
My `woodpecker.yml`:
```yml
variables:
- &PLUGIN_CUSTOM_1 gitea.example.com/my-org/my-repo:0 # fails: major
- &PLUGIN_CUSTOM_2 gitea.exampl…
-
### Component
other
### Describe the bug
Since https://github.com/woodpecker-ci/woodpecker/issues/1948 was fixed (yesterday), the json schema for `.woodpecker.yml` is out of date, but that is…