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.

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

ftl init fails with error: read-only file system #1770

Closed
safeer opened this issue Jun 13, 2024 · 1 comment · Fixed by #1771
Closed

ftl init fails with error: read-only file system #1770

safeer opened this issue Jun 13, 2024 · 1 comment · Fixed by #1771
Assignees
Labels
bug Something isn't working

Comments

@safeer
Copy link
Contributor

safeer commented Jun 13, 2024

Error when attempting to initialize a FTL Go module:

ftl init go . mymodule --log-level=DEBUG
debug: Unary RPC failed: unavailable: dial tcp [::1]:8892: connect: connection refused: /xyz.block.ftl.v1.AdminService/Ping
debug: Initializing FTL Go module mymodule in .
debug: Creating a new project config file at "/ftl-project.toml"
ftl: error: open /ftl-project.toml3523669785: read-only file system
@safeer safeer added the bug Something isn't working label Jun 13, 2024
@github-actions github-actions bot added the triage Issue needs triaging label Jun 13, 2024
@ftl-robot ftl-robot mentioned this issue Jun 13, 2024
@safeer
Copy link
Contributor Author

safeer commented Jun 13, 2024

Looks like DefaultConfigPath() walks up to the root of the filesystem if no config file exists, and attempts to create one there
cc @alecthomas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant