-
Notifications
You must be signed in to change notification settings - Fork 53
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
No path to region #374
Comments
you seem to be hitting #266, good news is a fix will be released soon. In the mean time you have to do |
The documentation says " |
This is one of those times where nomad-pack currently is different from the vanilla nomad cli. Hence this confusing behaviour which has bitten me more than once. But as i said the nomad team has fixed this in #366, coming to a nightly/release near you soon |
Ah I just realized that your |
Yep, I can confirm it's working on main branch. |
Hey @pschichtel,
Apologies for this, I'll look into the CI config to see what's going on there. Happy to hear |
I've setup two AUR package for nomad pack: nomad-pack-git (builds main) and nomad-pack-nightly (builds the nightly tag), so I'm covered for now :) |
Hi, I've not actually found helpful information and I feel like it might actually be a bug in nomad-pack:
I have a rather simple pack for an internal application. It contains just one template. When I render it and deploy it with
nomad job plan
andnomad job run
, then everything works fine as I'd expect it.However, if I use
nomad-pack plan
ornomad-pack run
directly, then I'm always presented with this output:Nomad client version:
v1.5.6
(fromnomad version
)Nomad server version:
1.5.6
(fromnomad server members
)Nomad-pack version:
v0.0.1-techpreview.4 (50d84d0)
(fromnomad-pack version
The text was updated successfully, but these errors were encountered: