Showing posts with label docker. Show all posts
Showing posts with label docker. Show all posts

Thursday, July 30, 2026

open-webui: Account Activation Pending

If you get the following error: Account Activation Pending
Contact Admin for WebUI Access
Your account status is currently pending activation.
To access the WebUI, please reach out to the administrator.
Admins can manage user statuses from the Admin Panel.
Admin: User (admin@localhost)

Open WebUI stores each account's role (pending, user, admin) in its SQLite database, and normally the very first account created is auto-promoted to admin — but if that didn't happen cleanly (e.g. a previous run, crash, or port conflict interfered), your account gets stuck as pending, which blocks access even with WEBUI_AUTH=False. The fix is to update that account's role directly in the database and then just refresh the browser tab.

docker exec -it open-webui python3 -c "
import sqlite3
conn = sqlite3.connect('/app/backend/data/webui.db')
c = conn.cursor()
c.execute(\"UPDATE user SET role='admin'\")
conn.commit()
print(c.rowcount, 'user(s) updated')
"

Friday, May 08, 2026

gentoo and distrobox: OCI runtime exec failed: exec failed: unable to start container process: error starting setns process: exec: already started

I have gentoo host, with systemd, nvidia and docker. When I want to create a distrobox image with systemd in the container, e.g.:
distrobox create --nvidia -i archlinux -n abox -H ~/home-abox --init --additional-packages "systemd"
I was getting: OCI runtime exec failed: exec failed: unable to start container process: error starting setns process: exec: already started
The solution was to use crun container runtime, instead of default runc. To do this

1. Install crun: emerge -av app-containers/crun
2. Create `/etc/docker/daemon.json` with the content: {
"runtimes": {
"crun": {
"path": "/usr/bin/crun"
}
},
"default-runtime": "crun"
}

3. Restart docker sudo systemctl restart docker

Friday, April 24, 2026

Open WebUI: Run as a temprorary container with Ollama support

docker run --rm --network=host -v open-webui:/app/backend/data -e OLLAMA_BASE_URL=http://127.0.0.1:11434 -e WEBUI_AUTH=False --name open-webui ghcr.io/open-webui/open-webui:main

Sunday, April 12, 2026

gentoo with systemd and docker: use Nvidia runtime in distrobox through Nvidia container oolkit

Install nvidia container toolbox: sudo emerge -av nvidia-container-toolkit restart docker service: sudo systemctl restart docker Create and setup /etc/cdi: mkdir -p /etc/cdi
nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
Check if its working: nvidia-ctk cdi list Configure docker to use NVIDIA runtime: sudo nvidia-ctk runtime configure --runtime=docker Restart docker service again: sudo systemctl restart docker Before creating distrobox container, lets just perfrom basic check if nvidia is avaiable in docker: docker run --rm --device=nvidia.com/gpu=all ubuntu nvidia-smi If this shows your Nvidia driver and info about your gpu, than it works.

Create distrobox that uses nvidia (fedora 43 as an example): distrobox create -i quay.io/fedora/fedora:43 -n fbox -H ~/home-fbox --additional-flags "--device=nvidia.com/gpu=all"
Enter the distrobox container, fbox, in this example, and test using nvidia-smi: sudo nvidia-smi This should also give info about your nvidia gpu and its driver.

If inside the distrobox container, nvidia is only avaiable for root user, you have to check what group number is nvidia on the host: stat -c "%g" /dev/nvidia0 This will show a number, e.g. 27.
Then in the distrobox container, fbox in this example, you have to edit /etc/group and:
1. add yourself (i.e. normal user) to video group 2. Change video group number to match the one on the host, e.g. 27. For example, /etc/group in fbox
video:x:27:your-user-name

Thursday, June 16, 2022

spark and notebook from docker

docker run --rm -p 10000:8888 jupyter/all-spark-notebook