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
1 - Create the following configuration file, change the token, access_key_id, secret_access_key and S3 bucket values accordingly and save it as snap.hcl:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Issue
panic: runtime error: invalid memory address running
nomad operator snapshot agent config.hcl
Reproduction Steps
1 - Create the following configuration file, change the token, access_key_id, secret_access_key and S3 bucket values accordingly and save it as snap.hcl:
2 - Run
nomad operator snapshot agent snap.hcl
:It fails with a runtime error.
3 - Add
local_storage
block to the config file and runnomad operator snapshot agent snap.hcl
again:It works as expected:
Expected behavior
It should not panic and, as per the documentation, only one storage block should be required.
Workaround: Add local_storage block to the config or pass -local-path argument to the CLI command.
Environment
The text was updated successfully, but these errors were encountered: