Archived
2
0

example firefox latest.

This commit is contained in:
Miroslav Šedivý 2022-01-02 19:32:44 +01:00
parent 52b2b6ed69
commit f37a2347e1
3 changed files with 6 additions and 6 deletions

View File

@ -1,7 +1,7 @@
# Getting started & FAQ # Getting started & FAQ
Use the following docker images: Use the following docker images:
- `m1k1o/neko:latest` - for Firefox. - `m1k1o/neko:latest` or `m1k1o/neko:firefox` - for Firefox.
- `m1k1o/neko:chromium` - for Chromium (needs `--cap-add=SYS_ADMIN`, see the [security implications](https://www.redhat.com/en/blog/container-tidbits-adding-capabilities-container)). - `m1k1o/neko:chromium` - for Chromium (needs `--cap-add=SYS_ADMIN`, see the [security implications](https://www.redhat.com/en/blog/container-tidbits-adding-capabilities-container)).
- `m1k1o/neko:google-chrome` - for Google Chrome (needs `--cap-add=SYS_ADMIN`, see the [security implications](https://www.redhat.com/en/blog/container-tidbits-adding-capabilities-container)). - `m1k1o/neko:google-chrome` - for Google Chrome (needs `--cap-add=SYS_ADMIN`, see the [security implications](https://www.redhat.com/en/blog/container-tidbits-adding-capabilities-container)).
- `m1k1o/neko:ungoogled-chromium` - for [Ungoogled Chromium](https://github.com/Eloston/ungoogled-chromium) (needs `--cap-add=SYS_ADMIN`, see the [security implications](https://www.redhat.com/en/blog/container-tidbits-adding-capabilities-container)) (by @whalehub). - `m1k1o/neko:ungoogled-chromium` - for [Ungoogled Chromium](https://github.com/Eloston/ungoogled-chromium) (needs `--cap-add=SYS_ADMIN`, see the [security implications](https://www.redhat.com/en/blog/container-tidbits-adding-capabilities-container)) (by @whalehub).

View File

@ -6,7 +6,7 @@
version: "3.4" version: "3.4"
services: services:
neko: neko:
image: "m1k1o/neko:latest" image: "m1k1o/neko:firefox"
restart: "unless-stopped" restart: "unless-stopped"
shm_size: "2gb" shm_size: "2gb"
ports: ports:

View File

@ -20,7 +20,7 @@ In following example, specified range `52000-52100` must be also exposed using d
version: "3.4" version: "3.4"
services: services:
neko: neko:
image: "m1k1o/neko:latest" image: "m1k1o/neko:firefox"
restart: "unless-stopped" restart: "unless-stopped"
shm_size: "2gb" shm_size: "2gb"
ports: ports:
@ -75,7 +75,7 @@ If your IP is not correct, you can specify own IP resover using `NEKO_IPFETCH`.
version: "3.4" version: "3.4"
services: services:
neko: neko:
image: "m1k1o/neko:latest" image: "m1k1o/neko:firefox"
restart: "unless-stopped" restart: "unless-stopped"
shm_size: "2gb" shm_size: "2gb"
ports: ports:
@ -96,7 +96,7 @@ Or you can specify your IP address manually using `NEKO_NAT1TO1`:
version: "3.4" version: "3.4"
services: services:
neko: neko:
image: "m1k1o/neko:latest" image: "m1k1o/neko:firefox"
restart: "unless-stopped" restart: "unless-stopped"
shm_size: "2gb" shm_size: "2gb"
ports: ports:
@ -121,7 +121,7 @@ To see verbose information from n.eko server, you can enable debug mode using `N
version: "3.4" version: "3.4"
services: services:
neko: neko:
image: "m1k1o/neko:latest" image: "m1k1o/neko:firefox"
restart: "unless-stopped" restart: "unless-stopped"
shm_size: "2gb" shm_size: "2gb"
ports: ports: