You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# API ConfigurationAPI_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxLOG_LEVEL=debugOPENAI_API_KEY="xxxxxxxxxxxxx"OPENAI_BASE_URL=http://0.0.0.0:8000/v1/# Server SettingsUVICORN_HOST=0.0.0.0UVICORN_PORT=8000# CORS SettingsALLOW_ORIGINS='["https://your-domain.example"]'# UI SettingsENABLE_UI=true# Whisper Model ConfigurationWHISPER__MODEL=organization/model-name-v3WHISPER__INFERENCE_DEVICE=cudaWHISPER__DEVICE_INDEX=[0,1]WHISPER__COMPUTE_TYPE=float16WHISPER__CPU_THREADS=8WHISPER__NUM_WORKERS=4WHISPER__TTL=600# Language SettingsDEFAULT_LANGUAGE=enDEFAULT_RESPONSE_FORMAT=json# Model PreloadingPRELOAD_MODELS='["organization/model-name-v3"]'# Performance-Optimized Timing SettingsMAX_NO_DATA_SECONDS=1.5MIN_DURATION=0.8WORD_TIMESTAMP_ERROR_MARGIN=0.15MAX_INACTIVITY_SECONDS=3.0INACTIVITY_WINDOW_SECONDS=6.0
Which is working well. I noticed that the API_KEY environment variable is not being respected or used. After inspecting the container's source, I noticed that the Docker Hub images need to be updated with the latest commits. This means that important changes, like the API_KEY functionality from c6b0d43, aren't available in the published Docker images.
To solve this and improve the experience in deployment, I'd suggest adding a GitHub Actions workflow to automatically build and publish Docker images on new releases. Here's a proposed workflow file:
name: Build and Push Docker Imageson:
release:
types: [published]workflow_dispatch:
jobs:
docker:
runs-on: ubuntu-lateststeps:
- name: Checkoutuses: actions/checkout@v4
- name: Set up QEMUuses: docker/setup-qemu-action@v3
- name: Set up Docker Buildxuses: docker/setup-buildx-action@v3
- name: Login to Docker Hubuses: docker/login-action@v3with:
username: ${{ secrets.DOCKERHUB_USERNAME }}password: ${{ secrets.DOCKERHUB_TOKEN }}
- name: Build and push CPU imageuses: docker/build-push-action@v5with:
context: .push: truetags: | fedirz/faster-whisper-server:latest fedirz/faster-whisper-server:${{ github.event.release.tag_name }}
- name: Build and push CUDA imageuses: docker/build-push-action@v5with:
context: .file: Dockerfile.cudapush: truetags: | fedirz/faster-whisper-server:latest-cuda fedirz/faster-whisper-server:${{ github.event.release.tag_name }}-cuda
This workflow would:
Automatically trigger when a new release is created
Build both CPU and CUDA versions of the image
Tag them with both latest and the release version
Push them to Docker Hub
To implement this, you would need to:
Add this file as .github/workflows/docker-publish.yml
Set up DOCKERHUB_USERNAME and DOCKERHUB_TOKEN secrets in the repository settings
Create a new release to trigger the workflow
This would ensure that users always have access to the latest features and fixes when using the Docker images.
The text was updated successfully, but these errors were encountered:
Maralai
changed the title
Security Issue with Docker
Security Issue with Docker (open API)
Nov 28, 2024
Maralai
changed the title
Security Issue with Docker (open API)
API_KEY environment variable not working in Docker image due to outdated build - Suggest adding GitHub Actions for automated releases
Nov 28, 2024
Please update the whisper server image in hub.docker.com . The image that is there does not support working with API_KEY. The new image is needed for deployment in runpod.io . Thank you.
@fedirz, could you update this on Docker Hub? I would love to deploy with the latest functionality and keep my containers updated with your latest official releases on docker. Please advise.
I have deployed this service as:
Which is working well. I noticed that the
API_KEY
environment variable is not being respected or used. After inspecting the container's source, I noticed that the Docker Hub images need to be updated with the latest commits. This means that important changes, like theAPI_KEY
functionality from c6b0d43, aren't available in the published Docker images.To solve this and improve the experience in deployment, I'd suggest adding a GitHub Actions workflow to automatically build and publish Docker images on new releases. Here's a proposed workflow file:
This workflow would:
latest
and the release versionTo implement this, you would need to:
.github/workflows/docker-publish.yml
DOCKERHUB_USERNAME
andDOCKERHUB_TOKEN
secrets in the repository settingsThis would ensure that users always have access to the latest features and fixes when using the Docker images.
The text was updated successfully, but these errors were encountered: