feat: troubleshooting section in hacking docs with publickey perm denied
ci/woodpecker/push/woodpecker Pipeline failed
Details
ci/woodpecker/push/woodpecker Pipeline failed
Details
parent
3ecd2289dc
commit
e8956ad068
|
@ -101,3 +101,24 @@ And provide information requested
|
||||||
```bash
|
```bash
|
||||||
make
|
make
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Troubleshooting
|
||||||
|
|
||||||
|
### Permission denied (publickey) in `make env`
|
||||||
|
|
||||||
|
`make env` runs `./integration/ci.sh init` which bootstraps a local
|
||||||
|
Gitea instance with some repositories for running tests. It also adds a
|
||||||
|
deploy SSH key, with read/write access to those repositories.
|
||||||
|
|
||||||
|
Please ensure the following:
|
||||||
|
|
||||||
|
1. The private key at [tests/fleet-deploy-key](../tests/fleet-deploy-key)
|
||||||
|
has `600` permissions. If not:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
chmod 600 tests/fleet-deploy-key
|
||||||
|
```
|
||||||
|
|
||||||
|
2. The Gitea instance listens at port 22, ensure it is listening on that
|
||||||
|
port. This can be verified by checking for orphan Gitea instances
|
||||||
|
and/or SSH daemons on that port.(TODO: listen SSH on different port)
|
||||||
|
|
Loading…
Reference in New Issue