Need some help on Drone + Gitea

Drone Support
1

I set up my Drone server in connection to Gitea, as explained here:
https://docs.drone.io/installation/providers/gitea/
https://docs.drone.io/installation/security/ssl/
https://docs.drone.io/runner/docker/installation/linux/

The good thing is, that everything seems to work. WebUI works. Authorization works, at least according to Drone API. Activating Drone CI per repository over WebUI works.

Bad thing is, that I activated a certain repository several times now, each time after I deleted the Drone containers and started anew (sometimes I also deleted the Database with Drone information).
On every activation, it starts the CI build. It shows it in the activity feed. All seems fine. But it never finishes. And reading the documentation, I don’t really know how to access the build logs (this does not work or I am doing it wrong) to see what is going on. Ultimately, the build runs forever, no matter what I change. Running docker logs drone-server and docker logs drone-runner respectively, does not yield any helpful information, at all.

What can I do? What logs can I access?

2

Solved by:

Undefined Platform when using Arm or Arm64

Drone assumes all pipelines are amd64 unless otherwise specified. If you are using Drone with arm or arm64 agents please be sure to specify the architecture to ensure builds are routed to the correct agent.

kind: pipeline
name: default

+platform:
+  os: linux
+  arch: arm

steps: ...

and

Basic Example

In the below example we demonstrate a pipeline that launches a Docker service container (Docker-in-Docker). The service container is run in privileged mode. For security reasons, only trusted repositories can enable privileged mode.

---
kind: pipeline
name: default

steps:
- name: test
  image: docker:dind
  volumes:
  - name: dockersock
    path: /var/run
  commands:
  - sleep 5 # give docker enough time to start
  - docker ps -a

services:
- name: docker
  image: docker:dind
  privileged: true
  volumes:
  - name: dockersock
    path: /var/run

volumes:
- name: dockersock
  temp: {}

and

Create the Primary Admin

When you setup the Drone server you have the ability to create the initial administrative account. If the account does not exist in the system it is automatically created on startup. This process is known as bootstrapping. This initial administrative account can be used to grant the administrator role to additional accounts.

The DRONE_USER_CREATE environment variable can be used to bootstrap the initial administrator. In the below example we provide the account username (e.g. github handle) with the admin flag set to true.

DRONE_USER_CREATE=username:octocat,admin:true

If you have an existing Drone installation and you need to bootstrap an administrative user, you can provide specify an existing username. Drone will update the account and grant administrator role on server restart.

and

only trusted repositories can enable privileged mode. To mark a repository as trusted, there is a checkbox in the repository settings that you need to enable. This checkbox is only available to system admins. To grant system admin access to a user see https://docs.drone.io/administration/user/admins/

Thanks to @bradrydzewski.