Support insecure VPN registry pulls
Build & Deploy / Build & Push Docker Image (push) Successful in 2m52s
Test / Type Check (all packages) (push) Successful in 50s
Build & Deploy / Deploy to VPS (push) Successful in 4s
Test / API Unit Tests (push) Successful in 49s
Test / Homepage Unit Tests (push) Successful in 42s
Test / Storefront Unit Tests (push) Successful in 39s
Test / Admin Unit Tests (push) Successful in 40s
Test / Dashboard Unit Tests (push) Successful in 41s
Test / API Integration Tests (push) Successful in 1m1s
Build & Deploy / Build & Push Docker Image (push) Successful in 2m52s
Test / Type Check (all packages) (push) Successful in 50s
Build & Deploy / Deploy to VPS (push) Successful in 4s
Test / API Unit Tests (push) Successful in 49s
Test / Homepage Unit Tests (push) Successful in 42s
Test / Storefront Unit Tests (push) Successful in 39s
Test / Admin Unit Tests (push) Successful in 40s
Test / Dashboard Unit Tests (push) Successful in 41s
Test / API Integration Tests (push) Successful in 1m1s
This commit is contained in:
@@ -50,10 +50,27 @@ APP_IMAGE=10.0.0.4/melabidi/carmanagement
|
||||
REGISTRY_HOST=10.0.0.4
|
||||
REGISTRY_USER=melabidi
|
||||
REGISTRY_TOKEN=<registry-token>
|
||||
REGISTRY_INSECURE=true
|
||||
IMAGE_ARCHIVE_DIR=
|
||||
IMAGE_ARCHIVE_REQUIRED=false
|
||||
```
|
||||
|
||||
Because Docker image names cannot include `http://`, the VPS Docker daemon must
|
||||
mark the registry as insecure before direct HTTP pulls. Add this entry to
|
||||
`/etc/docker/daemon.json`, merging it with any existing settings:
|
||||
|
||||
```json
|
||||
{
|
||||
"insecure-registries": ["10.0.0.4"]
|
||||
}
|
||||
```
|
||||
|
||||
Then restart Docker:
|
||||
|
||||
```bash
|
||||
sudo systemctl restart docker
|
||||
```
|
||||
|
||||
## VPN Container Image Handoff
|
||||
|
||||
This fallback is only needed if the VPS cannot reach `10.0.0.4` directly. If the
|
||||
|
||||
Reference in New Issue
Block a user