Unable to deploy my app using github actions

1

Hi there, I deployed my app on fly and it worked but when i tried to connect it with github actions, i get this error, logs:

image
image950×560 15.5 KB

image
image961×563 13.8 KB

image
image954×568 19.6 KB

image
image971×570 17.8 KB

Any suggestion pls?

2

Did you try changing npm install to npm install --unsafe-perm.

I never heard back if it worked here: error related to node-sass when trying to deploy the app with github workflow action - #3 by nadhirghn

3

It actually looks like node itself is inaccessible, not postinstall.js. We’ve replaced volta with node-build as the version manager for nodejs. You can try this new dockerfile template we use:

FROM debian:bullseye as builder

ENV PATH=/usr/local/node/bin:$PATH
ARG NODE_VERSION=18.15.0

RUN apt-get update; apt install -y curl python-is-python3 pkg-config build-essential && \
    curl -sL https://github.com/nodenv/node-build/archive/master.tar.gz | tar xz -C /tmp/ && \
    /tmp/node-build-master/bin/node-build "${NODE_VERSION}" /usr/local/node && \
rm -rf /tmp/node-build-master

RUN mkdir /app
WORKDIR /app

COPY . .

RUN npm install


FROM debian:bullseye-slim

LABEL fly_launch_runtime="nodejs"

COPY --from=builder /usr/local/node /usr/local/node
COPY --from=builder /app /app

WORKDIR /app
ENV NODE_ENV production
ENV PATH /usr/local/node/bin:$PATH

CMD [ "npm", "run", "start" ]
1 Like
6

Apologies for my delayed response. I attempted the solution you provided, but it was not successful. However, I made the necessary modifications to the dockerfile as suggested in the solution comment, and it worked. Thank you all for your help.

1 Like
7

Hi again, the deployment with github actions was successful, but the website is no longer accessible

image
image818×272 8.44 KB

image

8

Hi there, any update on this?

9

Hi,

Based on that most recent log it looks like the website is not accessible because connections are timing out. Assuming there are no issues with that particular Fly region …

Is your app responding on the expected port (often 8080)? With node there is likely some line to run a server and often it will default 3000. I’d make sure your fly.toml and node app ports are in sync with the used/expected port number.

Assuming they are, it may be the connection is working but is too slow to respond. Maybe add a route that does no work - just a simple res.send. That’s what I do. Checks the bare minimum, that the app is working and responding.

It may be worth sticking some debug log lines in there to see where it’s getting stuck. Even console.log lines, else GitHub - pinojs/pino: 🌲 super fast, all natural json logger.

10

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