# Juno Local Development Using a Docker Container

**URL:** <https://forum.dfinity.org/t/juno-local-development-using-a-docker-container/26199>\
**Category:** Developers\
**Created:** [January 4, 2024, 4:12pm UTC](https://forum.dfinity.org/t/juno-local-development-using-a-docker-container/26199 "2024-01-04T16:12:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\
**Post date:** [January 4, 2024, 4:12pm UTC](https://forum.dfinity.org/t/juno-local-development-using-a-docker-container/26199/1 "2024-01-04T16:12:48Z")

</div>

Hello 👋

I’m absolutely pumped to announce that Juno developers can now build locally and run E2E tests against a new Docker image.

This container performs the following tasks:

- It starts a local replica and icx-proxy
- A custom CLI deploys Internet Identity and Juno’s Satellite
- It applies a configuration that the dev can define with a config file
- That’s it! 🥳

So basically, you run `docker compose up` and you are all set!

* * *

`docker-compose.yml`:

```auto
services:
  juno-satellite:
    image: junobuild/satellite:latest
    ports:
      - 5987:5987
    volumes:
      - astro_dapp:/juno/.juno
      - ./juno.dev.json:/juno/juno.dev.json

volumes:
  astro_dapp:

```

A config file to apply settings to the Satellite smart contract:

```auto
{
  "satellite": {
    "collections": {
      "db": [
        {
          "collection": "counter",
          "read": "public",
          "write": "public",
          "memory": "stable"
        }
      ]
    }
  }
}

```

And basically just setting a variable to the unique initialization function:

```auto
await initJuno({
  satelliteId: import.meta.env.PUBLIC_SATELLITE_ID,
  container: true,
});

```

* * *

Blog post: [https://juno.build/blog/local-development](https://juno.build/blog/local-development)  
Documentation: [https://juno.build/docs/miscellaneous/local-development](https://juno.build/docs/miscellaneous/local-development)  
Repo: [https://github.com/junobuild/juno-docker](https://github.com/junobuild/juno-docker)

---

<div class="post-metadata">

**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\
**Post date:** [May 16, 2024, 1:31pm UTC](https://forum.dfinity.org/t/juno-local-development-using-a-docker-container/26199/2 "2024-05-16T13:31:11Z")

</div>

I’m thrilled to double down on Juno’s custom Docker-based solution by announcing that I have extended our DX by creating an image that can be used to develop Juno itself. 🔥

You need Node, Docker, and Rust (only if you plan to enhance the smart contracts).

From there, just clone the repo and install the dependencies:

```auto
git clone https://github.com/junobuild/juno
cd juno
npm ci

```

Then start the emulator aka the Docker container:

```auto
npm run emulator

```

In another terminal, start the frontend:

```auto
npm run dev

```

That’s it! You can start contributing to Juno. 💪

Feedback and potential reports of issues are most welcome.

No more dfx needed to develop anything Juno locally, let’s go! 🚀 😉

> **[GitHub - junobuild/juno: Build Web3 at Lightning Speed](https://github.com/junobuild/juno)**
>
> Build Web3 at Lightning Speed. Contribute to junobuild/juno development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\
**Post date:** [June 26, 2025, 12:46pm UTC](https://forum.dfinity.org/t/juno-local-development-using-a-docker-container/26199/3 "2025-06-26T12:46:33Z")

</div>

The [**Juno Emulator**](https://juno.build/docs/guides/local-development) for local development just got a big upskill 🚀💪

📦 New ARM Docker image - your Mac will thank you

⚡ Swapped the good old replica for PocketIC - faster & smoother UX

🧼 No more docker-compose clutter

The emulator is now configured in a `juno.config` file aka you can delete your `docker-compose.yml` file! 🥳

```auto
import {defineConfig} from '@junobuild/config';

export default defineConfig({
  satellite: {
    id: 'fmkjf-bqaaa-aaaal-acpza-cai',
    source: 'out',
  },
  emulator: {
    runner: {
      type: "docker",
      name: "my-custom-container-name"
    },
    skylab: {
      ports: {
        console: 5888
      }
    }
  }
});

```

🍒 Cherry on top?

This lays the foundation for supporting more (or different) runners in the future.

Have fun and let me know if anything acts weird!

 ![Epic Handshake 2](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/7/c/7c38c7e5de0486505f5f4c3a5df386fada05125c.jpeg)
