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
Invalid pack definition #346
Comments
I have a similar problem! I get a similar output as above with
I didn't see precompiled binaries for the other non-nightly versions... maybe the nightlies aren't compatible with the existing packs? edit: what I ended up doing, since I wanted to see nomad-pack work, is I went to https://github.com/hashicorp/nomad-pack-community-registry, cloned it, and removed the offending |
Which nomad-pack version? I get the same error when I use Docker tag "nomad-pack:0.0.1-techpreview.3", but if I compile the binary from sources then it works. Edit. I just realized that nightly builds go to a different Docker org. |
Same issue for me, was trying the nomad-ingress-nginx pack. |
i am also facing issue with this one and ended with this thread why there is problem with pack name with letter - |
Facing the same issue.
Is this expected behaviour? I can run this after removing integration block from metadata.hcl |
first time trying to explore nomad pack. after following the instruction to install on aws ec2 linux server, when run the command and nomad-packer registry list, all registry are invalid, i am using the latest nightly released rpm file
what does this mean?
------------------------------------+--------+-------------------------+----------+--------------------------------------------------
alertmanager@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
aws_efs_csi@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
boundary@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
chaotic_ngine@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
csi_openstack_cinder@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
drone@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
faasd@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
fabio@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
grafana@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
haproxy@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
hashicups@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
hello_world@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
influxdb@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
jaeger@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
jenkins@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
kibana@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
loki@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
nextcloud@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
nginx@latest | latest | Invalid pack definition | default | not parsable - registry contains no valid packs
The text was updated successfully, but these errors were encountered: