# Logstash is not up & running on MacOS

**URL:** <https://discuss.elastic.co/t/logstash-is-not-up-running-on-macos/346741>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [November 8, 2023, 7:49pm UTC](https://discuss.elastic.co/t/logstash-is-not-up-running-on-macos/346741 "2023-11-08T19:49:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![inandi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inandi/32/40801_2.png) [@inandi](https://discuss.elastic.co/u/inandi)\
**Post date:** [November 8, 2023, 7:49pm UTC](https://discuss.elastic.co/t/logstash-is-not-up-running-on-macos/346741/1 "2023-11-08T19:49:27Z")

</div>

(in Docker) Logstash is not running on MAC, but the same thing is working on Windows

getting below error

```auto
2023-11-09 01:12:57 runtime: failed to create new OS thread (have 2 already; errno=22)
2023-11-09 01:12:57 fatal error: newosproc
2023-11-09 01:12:57 
2023-11-09 01:12:57 runtime stack:
2023-11-09 01:12:57 runtime.throw(0x532c50, 0x9)
2023-11-09 01:12:57 /usr/local/go/src/runtime/panic.go:596 +0x95
2023-11-09 01:12:57 runtime.newosproc(0xc420028000, 0xc420038000)
2023-11-09 01:12:57 /usr/local/go/src/runtime/os_linux.go:163 +0x18c
2023-11-09 01:12:57 runtime.newm(0x53bb40, 0x0)
2023-11-09 01:12:57 /usr/local/go/src/runtime/proc.go:1628 +0x137
2023-11-09 01:12:57 runtime.main.func1()
2023-11-09 01:12:57 /usr/local/go/src/runtime/proc.go:126 +0x36
2023-11-09 01:12:57 runtime.systemstack(0x5c5c00)
2023-11-09 01:12:57 /usr/local/go/src/runtime/asm_amd64.s:327 +0x79
2023-11-09 01:12:57 runtime.mstart()
2023-11-09 01:12:57 /usr/local/go/src/runtime/proc.go:1132
2023-11-09 01:12:57 
2023-11-09 01:12:57 goroutine 1 [running]:
2023-11-09 01:12:57 runtime.systemstack_switch()
2023-11-09 01:12:57 /usr/local/go/src/runtime/asm_amd64.s:281 fp=0xc420024788 sp=0xc420024780
2023-11-09 01:12:57 runtime.main()
2023-11-09 01:12:57 /usr/local/go/src/runtime/proc.go:127 +0x6c fp=0xc4200247e0 sp=0xc420024788
2023-11-09 01:12:57 runtime.goexit()
2023-11-09 01:12:57 /usr/local/go/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc4200247e8 sp=0xc4200247e0

```

here is my logstash setup (docker-compose.yml)

```auto
logstash:
    container_name: $DOCKER_IMAGE_LOGSTASH
    platform: linux/amd64
    build:
      context: ./config/logstash/
      args:
        ELK_VERSION: $ELK_VERSION
    volumes:
      - type: bind
        source: ./config/logstash/config/logstash.yml
        target: /usr/share/logstash/config/logstash.yml
        read_only: true
      - type: bind
        source: ./config/logstash/pipeline
        target: /usr/share/logstash/pipeline
        read_only: true
      - type: bind
        source: ./app/logs/logstash/
        target: /var/log/logstash-data/
    ports:
      - "${LOGSTASH_TCP_PORT:-7001}:7001/tcp"
      - "${LOGSTASH_UDP_PORT:-7002}:7002/udp"
      - "${LOGSTASH_PORT:-9600}:9600"
    environment:
      LS_JAVA_OPTS: "-Xmx256m -Xms256m"
    networks:
      - elk
    depends_on:
      - elasticsearch

```

What to do?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [November 9, 2023, 1:11am UTC](https://discuss.elastic.co/t/logstash-is-not-up-running-on-macos/346741/2 "2023-11-09T01:11:32Z")

</div>

This is not a Logstash issue, but a Docker issue related to Apple Silicon chips.

Please check this issue on [Docker Github](https://github.com/docker/for-mac/issues/6137) with more details

I do not user Docker nor MacOS, but if I'm not wrong you need to use the [`arm64v8`](https://hub.docker.com/r/arm64v8/logstash/) images.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 7, 2023, 1:12am UTC](https://discuss.elastic.co/t/logstash-is-not-up-running-on-macos/346741/3 "2023-12-07T01:12:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.