You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cloned the repo and then use docker-compose up -d. The server is starting and I can access it but I cannot write a message.
here are the logs I got with docker-compose logs:
root@Morpheus:/home/darkwire# docker-compose up -d
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
Creating network "darkwire_db" with the default driver
Creating darkwire_redis_1 ... done
Creating darkwire_darkwire.io_1 ... done
root@Morpheus:/home/darkwire# docker-compose logs
Attaching to darkwire_darkwire.io_1, darkwire_redis_1
darkwire.io_1 | yarn run v1.22.4
darkwire.io_1 | $ cd server && CLIENT_DIST_DIRECTORY='../client/build' yarn start
darkwire.io_1 | $ node dist/src/index.js
darkwire.io_1 | Checking for inactive rooms...
darkwire.io_1 | Darkwire is online at port 3001
darkwire.io_1 | 0 rooms found
redis_1 | 1:C 10 May 2022 11:26:49.081 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 10 May 2022 11:26:49.082 # Redis version=6.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 10 May 2022 11:26:49.082 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 10 May 2022 11:26:49.087 * Running mode=standalone, port=6379.
redis_1 | 1:M 10 May 2022 11:26:49.087 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 10 May 2022 11:26:49.087 # Server initialized
redis_1 | 1:M 10 May 2022 11:26:49.087 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 10 May 2022 11:26:49.087 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 10 May 2022 11:26:49.089 * Ready to accept connections
here is what I have.
here are my docker-compose and Dockerfile (there is no modification from git repo)
root@Morpheus:/home/darkwire# cat docker-compose.yaml
version: '3.0'
services:
redis:
image: redis:6.0.6
networks:
- db
darkwire.io:
build:
context: .
networks:
- db
ports:
- 3001:3001
networks:
db:
root@Morpheus:/home/darkwire# cat Dockerfile
FROM node:14.7.0-stretch
# Installing yarn
RUN apt update -y && \
apt install yarn=v1.22.4 -v -y
USER node:node
# Server environmental variables will be put into server/.env
ENV MAILGUN_API_KEY=api-key \
MAILGUN_DOMAIN=darkwire.io \
[email protected] \
ABUSE_FROM_EMAIL_ADDRESS="Darkwire <[email protected]>" \
CLIENT_DIST_DIRECTORY='client/dist/path'\
ROOM_HASH_SECRET='some-uuid'\
SITE_URL=https://darkwire.io \
STORE_BACKEND=redis \
STORE_HOST=redis://redis:6379
# Client configuration will be put into client/.env
ENV TZ=UTC \
REACT_APP_API_HOST=localhost \
REACT_APP_API_PROTOCOL=http \
REACT_APP_API_PORT=3001 \
REACT_APP_COMMIT_SHA=some_sha \
REACT_APP_COMMIT_SHA=some_sha \
REACT_APP_MAX_FILE_SIZE=4
COPY --chown=node:node . .
RUN yarn build
STOPSIGNAL SIGINT
EXPOSE 3001
HEALTHCHECK --interval=30s --timeout=30s --start-period=10s --retries=3 \
CMD [ "curl", "-f", "${REACT_APP_API_PROTOCOL}://localhost:${REACT_APP_API_PORT}", "||", "exit", "1" ]
ENTRYPOINT [ "docker-entrypoint.sh" ]
CMD ["yarn", "start"]
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all and congratz for the project !
I have a small issue using docker-compose.
I cloned the repo and then use docker-compose up -d. The server is starting and I can access it but I cannot write a message.
here are the logs I got with docker-compose logs:
here is what I have.
here are my docker-compose and Dockerfile (there is no modification from git repo)
Did I miss something ?
thank you !
Beta Was this translation helpful? Give feedback.
All reactions