# Apple M1 지원 **URL:** \ **Category:** Feature\ **Created:** [6월 12, 2022, 4:31오후 UTC](https://meta.discourse.org/t/support-for-running-on-apple-m1/229724 "2022-06-12T16:31:33Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![titusc](https://avatars.discourse-cdn.com/v4/letter/t/9f8e36/32.png) [@titusc](https://meta.discourse.org/u/titusc)\ **Post date:** [6월 14, 2022, 3:49오후 UTC](https://meta.discourse.org/t/support-for-running-on-apple-m1/229724/9 "2022-06-14T15:49:22Z")
음, 그러니까 M1에서만 문제가 발생하는 것 같으니 ARM 기반 CPU라고 말한 내 말이 틀렸던 것 같습니다. 어쨌든 제가 한 작업은 다음과 같습니다 … 1. 새 브랜치 체크아웃 PR의 변경 사항을 적용하면 discourse-setup이 정상적으로 실행되지만, 이후 launcher가 실행되어 master에 최신 코드가 있는지 확인합니다. 그래서 새 브랜치를 체크아웃하고 변경 사항을 해당 새 브랜치에 적용했습니다. 또한 /etc/hosts에 항목을 추가하여, 제가 실행한다고 말한 도메인으로 실행 중인지 확인할 때 테스트를 통과하도록 했습니다. 2. discourse-setup 다시 실행 이번에는 launcher가 빌드를 수행하고 컨테이너를 시작하는 과정까지 모두 정상적으로 실행되었습니다. 아래는 출력 내용 중 후반부에 보이는 것입니다. [http://127.0.0.1로](http://127.0.0.xn--1-w30f) 접속해 보니 기본 nginx 페이지만 표시됩니다. 아마도 다른 문제들로 인해 M1에서는 결국 제대로 동작하지 않는 것 같습니다. 제대로 된 Intel 기반 시스템에서 테스트해 보겠습니다. 프로세스가 작동하는지, 포트 80/443에서 무언가가 리스닝하는지 확인하는 목적만으로는 괜찮지만, 실제로 페이지를 서빙할 수 있는 기능이 있다면 좋겠습니다. ![image](https://global.discourse-cdn.com/meta/original/4X/2/7/c/27c0673a8b26622c98473947c8f3e3fed069ac4c.png) ```plaintext I, [2022-06-14T15:29:42.810750 #1] INFO -- : Replacing (?-mix:#?ACCOUNT_EMAIL=.+) with ACCOUNT_EMAIL=$$ENV_LETSENCRYPT_ACCOUNT_EMAIL in /shared/letsencrypt/account.conf I, [2022-06-14T15:29:42.811886 #1] INFO -- : Replacing (?-mix:ssl_certificate_key.+) with ssl_certificate_key /shared/ssl/$$ENV_DISCOURSE_HOSTNAME.key; ssl_certificate_key /shared/ssl/$$ENV_DISCOURSE_HOSTNAME_ecc.key; in /etc/nginx/conf.d/discourse.conf I, [2022-06-14T15:29:42.812148 #1] INFO -- : Replacing (?-mix:add_header.+) with add_header Strict-Transport-Security 'max-age=63072000'; in /etc/nginx/conf.d/discourse.conf I, [2022-06-14T15:29:42.812430 #1] INFO -- : Replacing location @discourse { with location @discourse { add_header Strict-Transport-Security 'max-age=31536000'; # remember the certificate for a year and automatically connect to HTTPS for this domain in /etc/nginx/conf.d/discourse.conf I, [2022-06-14T15:29:42.813521 #1] INFO -- : > echo "Beginning of custom commands" I, [2022-06-14T15:29:42.814803 #1] INFO -- : Beginning of custom commands I, [2022-06-14T15:29:42.814856 #1] INFO -- : > echo "End of custom commands" I, [2022-06-14T15:29:42.816137 #1] INFO -- : End of custom commands I, [2022-06-14T15:29:42.818177 #1] INFO -- : Terminating async processes I, [2022-06-14T15:29:42.819361 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 57 2022-06-14 15:29:42.819 UTC [57] LOG: received fast shutdown request I, [2022-06-14T15:29:42.820068 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 118 118:signal-handler (1655220582) Received SIGTERM scheduling shutdown... 2022-06-14 15:29:42.829 UTC [57] LOG: aborting any active transactions 2022-06-14 15:29:42.832 UTC [57] LOG: background worker "logical replication launcher" (PID 66) exited with exit code 1 2022-06-14 15:29:42.835 UTC [61] LOG: shutting down 118:M 14 Jun 2022 15:29:42.866 # User requested shutdown... 118:M 14 Jun 2022 15:29:42.867 * Saving the final RDB snapshot before exiting. 118:M 14 Jun 2022 15:29:42.876 * DB saved on disk 118:M 14 Jun 2022 15:29:42.876 # Redis is now ready to exit, bye bye... 2022-06-14 15:29:42.958 UTC [57] LOG: database system is shut down sha256:5f552461c03594fde4b917c0e995c5f63a777b44ee1638e0367c22a29fe1ec16 ef60feb320f8684423dcb5c3ca6062226d937cd72a642485052fa641f15cbc01 + /usr/bin/docker run --shm-size=512m -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=4 -e UNICORN_SIDEKIQS=1 -e RUBY_GLOBAL_METHOD_CACHE_SIZE=131072 -e RUBY_GC_HEAP_GROWTH_MAX_SLOTS=40000 -e RUBY_GC_HEAP_INIT_SLOTS=400000 -e RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.5 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e LETSENCRYPT_DIR=/shared/letsencrypt -e DISCOURSE_FORCE_HTTPS=true -e LC_ALL=en_US.UTF-8 -e LANGUAGE=en_US.UTF-8 -e EMBER_CLI_PROD_ASSETS=1 -e DISCOURSE_HOSTNAME=dev.bogus.com -e DISCOURSE_DEVELOPER_EMAILS=support@bogus.com -e DISCOURSE_SMTP_ADDRESS=smtp-relay.gmail.com -e DISCOURSE_SMTP_PORT=587 -e DISCOURSE_SMTP_USER_NAME=support@bogus.com -e DISCOURSE_SMTP_PASSWORD=stupidpassword -e DISCOURSE_SMTP_DOMAIN=dev.bogus.com -e DISCOURSE_NOTIFICATION_EMAIL=noreply@dev.bogus.com -e LETSENCRYPT_ACCOUNT_EMAIL=me@example.com -h bogusdev-app -e DOCKER_HOST_IP=172.17.0.1 --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:f1:a1:42:8a:5f local_discourse/app /sbin/boot 0be6584a62912bae1d517882fde2a5bf61d1c39466448803be811fbd777c87a5 [root@bogusdev discourse]# [root@bogusdev discourse]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 0be6584a6291 local_discourse/app "/sbin/boot" 35 seconds ago Up 34 seconds 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp app [root@bogusdev discourse]# ``` --- _[View the full topic](https://meta.discourse.org/t/support-for-running-on-apple-m1/229724)._