Migrations/neko
1
0
Fork 0
mirror of https://github.com/m1k1o/neko.git synced 2026-11-03 00:11:48 -06:00
Code Issues Packages Projects Releases Wiki Activity

add docker image to migration.

Browse Source
This commit is contained in:
Miroslav Šedivý
2025-03-30 20:13:38 +02:00
parent 060b868826
commit 3e8169f9dc
3 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
webpage/docs/migration-from-v2/README.md
+8
View File
@@ -12,6 +12,14 @@ You can migrate to a new configuration even if you are using a V2 client. Just m
When using Neko in a container with a built-in client, the client will always be compatible with the server regardless of what configuration is used.
:::
## Docker Images {#docker}
Previously, neko was available primarily on Dockerhub as `m1k1o/neko`. While it stays as an option there, now the primary location is `ghcr.io/m1k1o/neko`.
ARM images were previously available as an flavor e.g. `m1k1o/neko:arm-firefox` or `ghcr.io/m1k1o/neko/arm-firefox`. Now, the ARM images are available as multi-arch images under the same tags as the amd64 images., e.g. `ghcr.io/m1k1o/neko/firefox`.
All applications available in the V2 images are also available in the V3 images. See the [Docker Images](/docs/v3/installation/docker-images) documentation for more details.
## Configuration {#config}
V3 is compatible with V2 configuration options when legacy support is enabled. You should be able to run V3 with the V2 configuration without any issues.