This Docker container packages AutoSubSync with all its dependencies, including a GUI accessible via web browser using PyQt6.
-
Navigate to the AutoSubSync directory:
cd AutoSubSync -
Create input and output directories:
mkdir -p input output desktop
-
Build and run the container:
docker-compose up --build -d
-
Access the GUI: Open your web browser and go to: http://localhost:6080
Click "Connect" in the noVNC interface to access the desktop.
For convenience, you can use the provided run scripts:
On macOS/Linux:
./run-docker.shOn Windows:
run-docker.bat- ✅ AutoSubSync GUI with PyQt6
- ✅ FFmpeg for media processing (included in assy)
- ✅ All synchronization tools (ffsubsync, autosubsync, alass)
- ✅ Web-based VNC interface (noVNC)
- ✅ Fluxbox window manager
- ✅ File manager for easy file operations
-
Access the application:
- Open http://localhost:6080 in your web browser
- Click "Connect" to access the desktop
- AutoSubSync will be running automatically
-
Upload files:
- Place your video and subtitle files in the
input/directory - They will be accessible within the container at
/app/input/ - Use the file manager in the VNC interface to navigate
- Place your video and subtitle files in the
-
Use AutoSubSync:
- The GUI works exactly like the desktop version
- Load your video and subtitle files
- Configure synchronization settings
- Process your subtitles
-
Download results:
- Processed files will appear in the
output/directory - Or save directly to Desktop (mapped to
desktop/directory)
- Processed files will appear in the
The container uses volume mounts to share files between your host system and the container:
./input/↔/app/input/- Place your input files here./output/↔/app/output/- Output files will appear here./desktop/↔/home/autosubsync/Desktop/- Desktop directory for the container
- ✅ Full AutoSubSync GUI accessible via web browser
- ✅ PyQt6 Qt framework
- ✅ All synchronization tools included (ffsubsync, autosubsync, alass)
- ✅ FFmpeg included for media processing
- ✅ No need to install dependencies on your host system
- ✅ Cross-platform (works on Windows, macOS, Linux)
- ✅ Persistent file access via volume mounts
The container runs multiple services managed by supervisor:
- Xvfb: Virtual display server
- Fluxbox: Lightweight window manager
- x11vnc: VNC server for display sharing
- noVNC: Web-based VNC client (websockify + web interface)
- AutoSubSync: The main application
The container uses PyQt6 directly from the assy package, which includes all necessary Qt dependencies for GUI operation in the Docker environment.
- 6080: Web-based VNC interface (primary access method)
- 5900: Direct VNC port (optional, for VNC clients)
# Check container logs
docker-compose logs
# Check specific service status
docker exec autosubsync supervisorctl status# Check AutoSubSync logs
docker exec autosubsync cat /var/log/supervisor/autosubsync.log
docker exec autosubsync cat /var/log/supervisor/autosubsync_error.logMake sure your input files are in the input/ directory and that you've created the necessary directories:
mkdir -p input output desktopRefresh the browser page or restart the container:
docker-compose restartIf the web interface doesn't load:
# Check if all services are running
docker exec autosubsync supervisorctl status
# Restart specific services if needed
docker exec autosubsync supervisorctl restart novncThe container runs a full desktop environment. For better performance:
- Ensure Docker has sufficient memory allocated (at least 2GB recommended)
- Close other resource-intensive applications
- Use Docker Desktop's resource settings to allocate more CPU/memory
If you prefer using a dedicated VNC client:
- Connect to
localhost:5900with your VNC client - No password is required
You can modify the display resolution by editing the docker/supervisord.conf file and changing the Xvfb screen parameter:
command=/usr/bin/Xvfb :0 -screen 0 1920x1080x24 -ac +extension GLX +render -noreset
To mount the source code for development:
docker-compose down
# Edit docker-compose.yml to add:
# - ./main:/app/main
docker-compose up --buildAccess the container for debugging:
# Get a shell in the container
docker exec -it autosubsync bash
# Check running processes
docker exec autosubsync ps aux
# Monitor supervisor logs
docker exec autosubsync tail -f /var/log/supervisor/supervisord.logThe Dockerfile includes all necessary dependencies:
- Python 3.11 slim base image
- System packages (Qt6, X11, VNC tools)
- Python packages from assy (PyQt6, ffsubsync, autosubsync, alass, static-ffmpeg, etc.)
- Supervisor for service management
Build process:
- Installs system dependencies
- Installs assy from PyPI (includes all dependencies and tools)
- Sets up services and permissions
- Docker and Docker Compose
- At least 2GB available RAM
- 2GB available disk space for the image
- Modern web browser for the VNC interface
- The container runs with a non-root user for the application
- No password is set for VNC (suitable for local use only)
- Services run on localhost only (not exposed to external networks)
- For production use, consider adding authentication and HTTPS
- Base Image: Python 3.11 on Debian Bookworm
- Qt Framework: PyQt6
- Supported Platforms: x86_64 Linux containers
- Host Systems: Windows, macOS, Linux (with Docker)
For issues specific to the Docker container:
- Check container logs:
docker-compose logs - Verify directories exist:
mkdir -p input output desktop - Ensure Docker has sufficient resources
- Check service status:
docker exec autosubsync supervisorctl status
For AutoSubSync application issues, refer to the main project documentation.
This Docker setup creates several files:
Dockerfile- Main container definitiondocker-compose.yml- Service orchestrationdocker/supervisord.conf- Service management configurationdocker/start.sh- Container startup scriptrun-docker.sh/run-docker.bat- Convenience run scripts.dockerignore- Build context exclusions