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 have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
I have removed any sensitive information from my code snippets and submission.
App Id
d3r3cld460f6i7
AWS Region
us-east-2
Amplify Hosting feature
SSR
Frontend framework
Next.js
Next.js version
13.5.5
Next.js router
Pages Router
Describe the bug
After deploying a seemingly innocuous change to my dev environment I started getting 500's. Redeploying old versions that we were previously working does not resolve the issue. The error in the compute logs show a readonly filesystem error:
ln: failed to create symbolic link ‘/tmp/app/amplify-compute-bundle-output/amplify-compute-bundle-output’: Read-only file system
Expected behavior
I expect to be able to deploy updates and/or revert to previous versions.
Reproduction steps
Deploy anything
Notice a 500 response with readonly filesystem errors in the log.
Build Settings
No response
Log output
# Put your logs below this line
ln: failed to create symbolic link ‘/tmp/app/amplify-compute-bundle-output/amplify-compute-bundle-output’: Read-only file system
Additional information
No response
The text was updated successfully, but these errors were encountered:
Before opening, please confirm:
App Id
d3r3cld460f6i7
AWS Region
us-east-2
Amplify Hosting feature
SSR
Frontend framework
Next.js
Next.js version
13.5.5
Next.js router
Pages Router
Describe the bug
After deploying a seemingly innocuous change to my dev environment I started getting 500's. Redeploying old versions that we were previously working does not resolve the issue. The error in the compute logs show a readonly filesystem error:
Expected behavior
I expect to be able to deploy updates and/or revert to previous versions.
Reproduction steps
Build Settings
No response
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: