forked from Icycoide/searxng
86373e7c87
Instead of using Wolfi base images from cgr.dev and making that mess on the Dockerfile, why don't we build the base images ourselves from Wolfi repos with apko? The intention of this is to simplify the main Dockerfile and avoid having to patch the base image every time, it also simplifies some steps like image ownership management and provides extremely fast builds.
61 lines
1 KiB
YAML
61 lines
1 KiB
YAML
contents:
|
|
keyring:
|
|
- https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
|
|
repositories:
|
|
- https://packages.wolfi.dev/os
|
|
packages:
|
|
- wolfi-baselayout
|
|
- ca-certificates-bundle
|
|
- busybox
|
|
- python-3.13
|
|
# healthcheck
|
|
- wget
|
|
# uwsgi
|
|
- mailcap
|
|
|
|
entrypoint:
|
|
command: /bin/sh -l
|
|
|
|
work-dir: /usr/local/searxng/
|
|
|
|
accounts:
|
|
groups:
|
|
- groupname: searxng
|
|
gid: 977
|
|
users:
|
|
- username: searxng
|
|
uid: 977
|
|
shell: /bin/ash
|
|
|
|
environment:
|
|
PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
|
|
SSL_CERT_FILE: /etc/ssl/certs/ca-certificates.crt
|
|
HISTFILE: /dev/null
|
|
CONFIG_PATH: /etc/searxng
|
|
DATA_PATH: /var/cache/searxng
|
|
|
|
paths:
|
|
# Workdir
|
|
- path: /usr/local/searxng/
|
|
type: directory
|
|
uid: 977
|
|
gid: 977
|
|
permissions: 0o755
|
|
|
|
# Config volume
|
|
- path: /etc/searxng/
|
|
type: directory
|
|
uid: 977
|
|
gid: 977
|
|
permissions: 0o755
|
|
|
|
# Data volume
|
|
- path: /var/cache/searxng/
|
|
type: directory
|
|
uid: 977
|
|
gid: 977
|
|
permissions: 0o755
|
|
|
|
archs:
|
|
- x86_64
|
|
- aarch64
|