Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"FLY_APP_NAME is not set" on upgrade #262

Closed
Jonher937 opened this issue May 21, 2024 · 1 comment · Fixed by #263
Closed

"FLY_APP_NAME is not set" on upgrade #262

Jonher937 opened this issue May 21, 2024 · 1 comment · Fixed by #263

Comments

@Jonher937
Copy link
Contributor

Hi, due to the addition of the fly-wrapper and it being set as the default entrypoint here:

upterm/Dockerfile.uptermd

Line 42 in 1846c3a

ENTRYPOINT ["uptermd-fly"]
upgrade of upterm fails unless the user overrides the entrypoint.

Easy fix for someone that can figure that out, but would have been great to menton in changelog if it was not defaulted to by accident.

A user can override the entrypoint back to uptermd to pass upgrade.
@owenthereal owenthereal mentioned this issue May 21, 2024
Merged
@owenthereal
Copy link
Owner

This is not desired. I fixed it in #263. Please wait for the new release 0.14.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't override Dockerfile entrypoint with uptermd-fly owenthereal/upterm
2 participants
@owenthereal @Jonher937