[help / machine fails] node compatibility

Questions / Help Build debugging
,
1

I am running my application which is just soketi which uses uWebSockets.

My machine fails to deploy with these logs

throw new Error('This version of uWS.js supports only Node.js 14, 16 and 18 on (glibc) Linux, macOS and Windows, on Tier 1 platforms (https://github.com/nodejs/node/blob/master/BUILDING.md#platform-list).\n\n' + e.toString());

I installed Node 18. I presume the Fly Machine platform is compatible with node and their platform list

Is there any additional configuration needed to be done to get Node to work on the Fly Machine?

My steps were to 1) create a soketi.conf file 2) create a Dockerfile file 3) run command fly launch.

I have my soketi.conf file with

[program:soketi]
process_name=%(program_name)s_%(process_num)02d
command=soketi start
autostart=true
autorestart=true
stopasgroup=true
killasgroup=true
user=root
numprocs=1
redirect_stderr=true
stdout_logfile=/var/log/soketi-supervisor.log
stopwaitsecs=60
stopsignal=sigint
minfds=10240

and my Dockerfile with

FROM node:18-alpine

# Install necessary packages
RUN apk add --no-cache git python3 gcc supervisor

# Set up global npm directory and permissions
RUN mkdir -p /usr/local/n
RUN chmod -R 777 /usr/local/n

# Set the working directory
WORKDIR /usr/src/app

# Install soketi globally
RUN npm install -g @soketi/soketi

# Copy Supervisor configuration
COPY soketi.conf /etc/supervisor/conf.d/soketi.conf

# Expose the port soketi will run on
EXPOSE 6001

# Command to start Supervisor, which will manage soketi
CMD ["supervisord", "-c", "/etc/supervisor/supervisord.conf"]

Then ran fly deploy

2

Hi… I think it might be complaining specifically about glibc. Last I heard, Alpine either didn’t support that—or required a lot of hoops to be jumped through first.

Hope this helps a little!

1 Like
3

Hi. Okay, thanks. I added gcompat for the glibc compatibility and added a default supervisor.conf file generated from echo_supervisord_conf.

My Dockerfile is

FROM node:18-alpine

# Install necessary packages
RUN apk add --no-cache git python3 gcc gcompat supervisor

# Set up global npm directory and permissions
RUN mkdir -p /usr/local/n
RUN chmod -R 777 /usr/local/n

# Set the working directory
WORKDIR /usr/src/app

# Install soketi globally
RUN npm install -g @soketi/soketi

# Copy Supervisor configuration files
COPY supervisord.conf /etc/supervisor/supervisord.conf
COPY soketi.conf /etc/supervisor/soketi.conf

# Ensure correct permissions for Supervisor config
RUN chmod 644 /etc/supervisor/supervisord.conf
RUN chmod 644 /etc/supervisor/soketi.conf

# Expose the port soketi will run on
EXPOSE 6001

# Command to start Supervisor, which will manage soketi
CMD ["supervisord", "-c", "/etc/supervisor/supervisord.conf"]

My soketi.conf file

[program:soketi]
process_name=%(program_name)s_%(process_num)02d
command=soketi start
autostart=true
autorestart=true
stopasgroup=true
killasgroup=true
user=root
numprocs=1
redirect_stderr=true
stdout_logfile=/var/log/soketi-supervisor.log
stopwaitsecs=60
stopsignal=sigint
minfds=10240

My supervisord.conf file

[unix_http_server]
file=/tmp/supervisor.sock

[supervisord]
logfile=/tmp/supervisord.log
logfile_maxbytes=50MB
logfile_backups=10
loglevel=info
pidfile=/tmp/supervisord.pid
nodaemon=false
silent=false
minfds=1024
minprocs=200

[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl=unix:///tmp/supervisor.sock

[include]
files = /etc/supervisor/soketi.conf

My Fly Machine live logs

[ 0.274033] PCI: Fatal: No config space access function found
INFO Starting init (commit: f7402432)...
INFO Preparing to run: `docker-entrypoint.sh supervisord -c /etc/supervisor/supervisord.conf` as root
INFO [fly api proxy] listening at /.fly/api
2024/06/19 05:13:25 INFO SSH listening listen_address=[fdaa:9:7227:a7b:1ac:ab97:c7a2:2]:22 dns_server=[fdaa::3]:53
Machine started in 727ms
INFO Main child exited normally with code: 0
INFO Starting clean up.
WARN could not unmount /rootfs: EINVAL: Invalid argument
[ 1.624185] reboot: Restarting system
machine exited with exit code 0, not restarting

What do the errors and warnings mean and how come the machine exits without restarting?

4

Try setting that to true.

1 Like
5

Thanks! My machine now continues to run instead of exiting immediately. I also updated my fly.toml file to have a minimum of one machine running so it continually runs as I want instead of exiting after a few minutes of no traffic.

[[services]]
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 1
1 Like