10 months ago
Have tried to change a few env but it turns to deployment error
Though I restored the previous env configs, it still fails to deploy
ⓘ Deployment information is only viewable by project members and Railway employees.
25 Replies
10 months ago
Full build and deploy logs please - https://bookmarklets.up.railway.app/log-downloader/
10 months ago
This docker image
https://hub.docker.com/r/ubuntu/squid
10 months ago
I didn't specified any tag. Just typed "ubuntu/squid" on Railway.
You can see the attached screenshot.
Attachments
10 months ago
This likely means something on the service is misconfigured, try deploying into a new service.
10 months ago
Are you sure you have the right start command specified? It looks like it's erroring out when attempting to run your start command
Status changed to Awaiting User Response railway[bot] • 10 months ago
10 months ago
I've set the command based on the document by Dify and it has no problem with deployment.
Status changed to Awaiting Railway Response railway[bot] • 10 months ago
10 months ago
"sh", "-c", "cp /docker-entrypoint-mount.sh /docker-entrypoint.sh && sed -i 's/\r$$//' /docker-entrypoint.sh && chmod +x /docker-entrypoint.sh && /docker-entrypoint.sh"
10 months ago
Unfortunately I don't know the detail because it's written on Dify's document. But I'm guessing this is only required on the initial service creation. I've deleted this custom start command and tried deploy then it doesn't crash so far.
10 months ago
What is this proxy needed for exactly?
The template doesn't use it? - https://railway.app/template/V1xiql
10 months ago
It's required to setup on latest Dify version. The template you refer has made based on old Dify version.
10 months ago
Thanks! @jack would be the best person to optimize and update the template to fit to the latest version.
10 months ago
Hey, Jack said his template does not deploy an older version, perhaps you are wanting some different configurations?
Could you link me to some docs on the subject please?
10 months ago
Brody, thanks for checking with Jack.
The template made by Jack has set Dify-related docker image source to Dify's official one and those are keep updating by Dify team. But after v0.6.12, Dify added new docker image called "Sandbox" which is not included in Jack's template.
The reason why I made the another template is to fix the issue discussed on the thread below. It's not solved by anyone yet.
https://help.railway.app/templates/dify-a02ad146
Here is the list of issue I'm gonna solve for making Dify on Railway works properly.
Uploaded files in Knowledge are queuing with 0%
"Failed to execute code, which is likely a network issue, please check if the sandbox service is running. ( Error: [Errno 111] Connection refused )" on template block (Dify's feature, not Railway's one)
10 months ago
Gotcha, thank you for this information, I will speak to Jack again and hopefully, I can get him to attempt fixing his template again, as the team is also interested in getting this template working.
I would ask that you not attempt to make and publish a pre-existing template until you have confirmation that the template has been abandoned.
10 months ago
Happy to hear that your team is interested in Dify template.
> I would ask that you not attempt to make and publish a pre-existing template until you have confirmation that the template has been abandoned.
Yes, I did't publish my Dify template publicly because the original one has made by Jack.
Have a great weekend!