专属域名
文档搜索
轩辕助手
Run助手
邀请有礼
返回顶部
快速返回页面顶部
收起
收起工具栏
轩辕镜像 官方专业版
轩辕镜像 官方专业版轩辕镜像 官方专业版官方专业版
首页个人中心搜索镜像

交易
充值流量我的订单
工具
提交工单镜像收录一键安装
Npm 源Pip 源Homebrew 源
帮助
常见问题
其他
关于我们网站地图

官方QQ群: 1072982923

evolutecx/firebase-emulator Docker 镜像 - 轩辕镜像

firebase-emulator
evolutecx/firebase-emulator
A dockerized firebase emulator setup that persists existing emulator data across runs
0 次下载
⏱️ 镜像拉取更稳定,部署项目不再心跳加速
镜像简介版本下载
⏱️ 镜像拉取更稳定,部署项目不再心跳加速

firebase-emulator-docker

A dockerized firebase emulator setup, that actually exports existing data when the container shuts down and re-imports data when the container starts up again *

We created this image because [***] failed to export and restore emulator state and they didnt publish a configurable Dockerfile

* In order to make this export/import work, a volume is needed - see below "Persisting data"

How to use:

docker-compose
  1. Clone the repo
  2. Enter your Firebase Project ID as environment variable FB_PROJECT_ID in the docker-compose.yml-File
  3. cd into the cloned directory
  4. Run docker-compose up in that directory to spin up the emulators (this has a volume definition for exporting and importing data - see "Persisting Data" to understand what this means 😉)
docker run

you can use ordinary docker-commands like so: (Important: You need to specify your Firebase Project ID with the environment variable FB_PROJECT_ID)

sh
docker run -d \
  --name firebase-emulator \
  -e FB_PROJECT_ID=[your_project_id] \
  evolutecx/firebase-emulator:latest
Supported architectures

From beginning of version 0.0.3 the pre-built images support linux/amd64, linux/arm64, linux/ppc64le and linux/s390x out of the box. By the time of this release this was all the architectures we could build for based on the latest node-18-alpine image.

Versions up to 0.0.2 only support linux/amd64 (which results in poor performance when running on apple silicon chips) - the change from version 0.0.2 to 0.0.3 is actually only the multi-architecture build, nothing else, so upgrading to 0.0.3 should be safe.

The right architecture will be used during container creation.

If you need more architectures to be suppported let us know on our github.

You can also build your own Image for more architectures

Adresses

The emulators will be available under these addresses:

  • Emulator UI: http://localhost:4000
  • Auth Emulator: http://localhost:9099
  • Firestore Emulator: http://localhost:8080
  • Functions Emulator: http://localhost:5001
  • Cloud Storage Emulator: http://localhost:9199
  • Realtime DB Emulator: http://localhost:9000

Configuring Ports

By default the emulator exposes these ports:

  • firestore: 8080
  • ui: 4000
  • auth: 9099
  • functions: 5001
  • database: 9000
  • storage: 9199

To change the ports on your host, just specify them in your docker- or docker-compose-command like so:

sh
docker run -d \
  --name firebase-emulator \
  -p ***:8080 \
  -p ***:4000 \
  -p ***:9099 \
  -p ***:5001 \
  -p ***:9000 \
  -p ***:9199 \
  -e FB_PROJECT_ID=[your_project_id] \
  evolutecx/firebase-emulator:latest

or with docker-compose

yaml
services:
  firebase-emulator:
    image: evolutecx/firebase-emulator:latest
    ports:
      - ***:8080 #Firestore
      - ***:4000 #Emulator UI
      - ***:9099 #Firebase Auth
      - ***:9199 #Firebase Cloud Storage
      - ***:9000 #Firebase Realtime database
    environment:
      - FB_PROJECT_ID=[YOUR_PROJECT_ID]

In this example we map port *** on the host to port 8080 on the container (and also for all the other ports)

Persisting Data

The container is configured in a way that it exports all data to /firebase/data/export on shutdown and re-imports it from there during startup.

In order to persist data between runs, a volume is needed.

IMPORTANT: The volume should mount to /firebase/data in the container, do NOT explicitly mount to /firebase/data/export, as the emulator will error with Export failed: dest already exists

With Docker

Define a named volume that points to the /firebase/data-folder in the container.

sh
docker run -d \
  --name firebase-emulator \
  -v ./firebase_data:/firebase/data \
  -e FB_PROJECT_ID=[your_project_id] \
  evolutecx/firebase-emulator:latest
with docker-compose:

Make sure you define a volume-section for your service in your docker-compose file, like so:

yaml
services:
  firebase-emulator:
    container_name: firebase-emulator
    image: evolutecx/firebase-emulator:latest
    restart: always
    ports:
      - 4000:4000 #Emulator UI
      - 9099:9099 #Firebase Auth
      - 8080:8080 #Firestore
      - 9199:9199 #Firebase Cloud Storage
      - 9000:9000 #Firebase Realtime database
    environment:
      - FB_PROJECT_ID=[YOUR_PROJECT_ID]
    volumes:
      - ./firebase-data:/firebase/data:rw # <- this stores data on shutdown to ./firebase-data/data/export on your host

Building for more architectures

From beginning of version 0.0.3 the pre-built images support linux/amd64, linux/arm64, linux/ppc64le and linux/s390x out of the box. By the time of this release this was all the architectures we could build for based on the latest node-18-alpine image.

You can try building a new version of the image and pushing it to dockerhub yourself: docker buildx build --platform linux/amd64,linux/arm64,[other_architectures_you_want_to_support] -t [username]/[image]:[version] .

More information here: [***]

Contribution

Feel free to fork the repo and create Merge requests to our repo. Otherwise feel free to create an issue and we will have a look.

查看更多 firebase-emulator 相关镜像 →
airbyte/firebase-emulator logo
airbyte/firebase-emulator
暂无描述
406 pulls
上次更新:未知
sa2taka/firebase-emulator logo
sa2taka/firebase-emulator
暂无描述
100K+ pulls
上次更新:未知
goatlab/firebase-emulator logo
goatlab/firebase-emulator
即开即用的Firebase模拟器基础镜像,用于本地开发和测试Firebase服务,默认启用所有模拟器并支持自定义配置。
250K+ pulls
上次更新:未知
emitwise/firebase-emulator logo
emitwise/firebase-emulator
暂无描述
10K+ pulls
上次更新:未知

轩辕镜像配置手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

登录仓库拉取

通过 Docker 登录认证访问私有仓库

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

Docker Compose

Docker Compose 项目配置

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

MacOS OrbStack

MacOS OrbStack 容器配置

宝塔面板

在宝塔面板一键配置镜像

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

极空间

极空间 NAS 系统配置服务

爱快路由

爱快 iKuai 路由系统配置

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

专属域名拉取

无需登录使用专属域名

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

轩辕镜像免费版与专业版有什么区别?

免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。

轩辕镜像支持哪些镜像仓库?

专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。

流量耗尽错误提示

当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。

410 错误问题

通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。

manifest unknown 错误

先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。

镜像拉取成功后,如何去掉轩辕镜像域名前缀?

使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
evolutecx/firebase-emulator
官方博客Docker 镜像使用技巧与技术博客
热门镜像查看热门 Docker 镜像推荐
一键安装一键安装 Docker 并配置镜像源
咨询镜像拉取问题请 提交工单,官方技术交流群:1072982923
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
咨询镜像拉取问题请提交工单,官方技术交流群:
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
官方邮箱:点击复制邮箱
©2024-2026 源码跳动
官方邮箱:点击复制邮箱Copyright © 2024-2026 杭州源码跳动科技有限公司. All rights reserved.