R
Railway13mo ago
bo

Nixpacks Deployment Error

Trying to deploy a service i've deployed plenty of times before and now I'm getting the following error: "ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 1f70767f-cf58-441a-8eff-a3752eac8501::ack54q9o32afi4ir84x12lrkc: "/.nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix": not found" Here are the full logs:
Using Nixpacks

==============


context: c48a45c01120ba871156e05598c0b792



╔══════════════ Nixpacks v1.19.0 ═════════════╗

║ setup │ nodejs_18, yarn-1_x ║

║─────────────────────────────────────────────║

║ install │ yarn install --frozen-lockfile ║

║─────────────────────────────────────────────║

║ build │ yarn run build ║

║─────────────────────────────────────────────║

║ start │ yarn run start ║

╚═════════════════════════════════════════════╝





#0 building with "default" instance using docker driver



#1 [internal] load .dockerignore

#1 transferring context: 154B done

#1 DONE 0.1s



#2 [internal] load build definition from Dockerfile



#2 transferring dockerfile: 2.45kB done

#2 DONE 0.1s



#3 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1699920194



#3 DONE 0.2s



#4 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1699920194@sha256:c861ec45a7401768f59183a4a51056daf7dd26ab9a5215836c81b09725b9cbb6

#4 DONE 0.0s





#5 [internal] load build context

#5 transferring context: 84.51kB done

#5 DONE 0.0s



#6 [stage-0 2/10] WORKDIR /app/

#6 CACHED



#7 [stage-0 3/10] COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix

#7 ERROR: failed to calculate checksum of ref 1f70767f-cf58-441a-8eff-a3752eac8501::ack54q9o32afi4ir84x12lrkc: "/.nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix": not found

-----



> [stage-0 3/10] COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix:

-----

Dockerfile:7

-------------------

5 |

6 |

7 | >>> COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix

8 | RUN nix-env -if .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix && nix-collect-garbage -d
Using Nixpacks

==============


context: c48a45c01120ba871156e05598c0b792



╔══════════════ Nixpacks v1.19.0 ═════════════╗

║ setup │ nodejs_18, yarn-1_x ║

║─────────────────────────────────────────────║

║ install │ yarn install --frozen-lockfile ║

║─────────────────────────────────────────────║

║ build │ yarn run build ║

║─────────────────────────────────────────────║

║ start │ yarn run start ║

╚═════════════════════════════════════════════╝





#0 building with "default" instance using docker driver



#1 [internal] load .dockerignore

#1 transferring context: 154B done

#1 DONE 0.1s



#2 [internal] load build definition from Dockerfile



#2 transferring dockerfile: 2.45kB done

#2 DONE 0.1s



#3 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1699920194



#3 DONE 0.2s



#4 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1699920194@sha256:c861ec45a7401768f59183a4a51056daf7dd26ab9a5215836c81b09725b9cbb6

#4 DONE 0.0s





#5 [internal] load build context

#5 transferring context: 84.51kB done

#5 DONE 0.0s



#6 [stage-0 2/10] WORKDIR /app/

#6 CACHED



#7 [stage-0 3/10] COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix

#7 ERROR: failed to calculate checksum of ref 1f70767f-cf58-441a-8eff-a3752eac8501::ack54q9o32afi4ir84x12lrkc: "/.nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix": not found

-----



> [stage-0 3/10] COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix:

-----

Dockerfile:7

-------------------

5 |

6 |

7 | >>> COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix

8 | RUN nix-env -if .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix && nix-collect-garbage -d
Solution:
please try this simple Dockerfile ```dockerfile FROM node:18.17.1 WORKDIR /app...
Jump to solution
10 Replies
Percy
Percy13mo ago
Project ID: 1f70767f-cf58-441a-8eff-a3752eac8501,1f70767f-cf58-441a-8eff-a3752eac8501
bo
boOP13mo ago
Would appreciate a reply as my company requires this service to run properly and I haven’t been able to deploy it in more than a day 😄 @Brody
Brody
Brody13mo ago
#🛂|readme #5
Adam
Adam13mo ago
Please don’t ping conductors or team members. You’re on the pro plan, you’re entitled to help directly from the team through [email protected]. Given that it’s the weekend, the team will not respond until monday. Please provide more information as well as your full build logs. I do not see an error in the logs you sent. https://bookmarklets.up.railway.app/log-downloader/
bo
boOP12mo ago
I’ve pinged even though I saw that rule because it was (and still is) an emergency. I too run a community discord for my business and people tag me all the time even though it’s against the rules, but more often than not I’ll reply to their question instead of linking them to the rules as that usually is the best course of actions to keep customers happy and to actually help them. I’ve posted this Friday not Saturday, and I saw team members replying to other questions after my question was already posted and I still didn’t get a reply. You guys don’t work on weekends and even though that’s weird for a hosting company to not offer support during the weekend, I understand given it’s a small company. However to get support before Monday it seems to me like I would have needed to post this Thursday? It just seems very weird to me that railway’s support has gone downhill so fast in such a small amount of time, seems like it was just yesterday we had 1 on 1 tickets for the pro plan. All in all as a user of railway for a while I’m sad to see the service keep declining instead of improving. At some point the small cost savings will no longer make it worth it for businesses such as mine to switch from bigger providers that have less issues and better support. With that being said, I have attached the logs with this message. Hopefully this can be fixed soon after 3 days of not being able to deploy my service.
Brody
Brody12mo ago
there's a big difference between giving constructive feedback and just saying something is bad, you unfortunately, are doing the latter. this is community help, please be respectful and kind in what you say.
Solution
Brody
Brody12mo ago
please try this simple Dockerfile
FROM node:18.17.1

WORKDIR /app

COPY package.json yarn.lock ./

RUN yarn install --frozen-lockfile

COPY . ./

RUN yarn run build

CMD ['yarn', 'run', 'start']
FROM node:18.17.1

WORKDIR /app

COPY package.json yarn.lock ./

RUN yarn install --frozen-lockfile

COPY . ./

RUN yarn run build

CMD ['yarn', 'run', 'start']
bo
boOP12mo ago
I don’t think I was disrespectful in any way whatsoever, I’m just sharing my honest opinion as someone who has been using railway for a while. I do believe all I’ve said was constructive criticism and I meant no harm in any way, it’s just just my experience dealing with railway for the past couple of months. Locally or do I add it to my service and deploy it in railway?
Brody
Brody12mo ago
add it to your project and push the changes
Adam
Adam12mo ago
Reading this over, there are a few points I would like to clarify. This server is community help, open to all Railway users. Brody and I are just members of the community who are active in this server alleviating the strain on the Team's inboxes. 1-on-1 tickets for pro plan never existed. Pro plan users are eligible for support through the [email protected] email address, as I said in my message above. However, there is no response SLA with requests to said email. The team will do their best to help you out, but if it's not a platform issue they will likely direct you here. As mentioned, the team does not work weekends. Yes, this would be odd for a large company, but Railway only has <20 employees. For a small startup, they're pulling amazing numbers, but those numbers don't justify a dedicated 24/7 support staff. That being said, I believe the Enterprise Plan does receive an SLA when it comes to support requests. However, most teams do not fall under this bucket. Unless you are willing to commit to a $10k+ annual spend on Railway, the plan is not for you. In the future, it's worth posting your questions here in case we are able to fix them. If you do not receive a response within the day, chances are your ticket got buried and it is safe to post another. We are very, very familiar with the platform and work extremely closely with the team. However, if we are not able to solve your issue, the [email protected] line is always available to you.
Want results from more Discord servers?
Add your server