semconvgen: unable to access specifcation data due to incorrect selinux file labels

[frzifus]

Enforced selinux policies can cause issues when files get shared with a containerized process. Since file permissions are reflected by this labels[0]. Docker/Podman have the ability to relabel[1] shared files.

0: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/security-enhanced_linux/sect-security-enhanced_linux-working_with_selinux-selinux_contexts_labeling_files
1: https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label

---

Generating semconv 1.16.0 on fedora 37.

$ make gensemconv SPECPATH=../opentelemetry-specification SPECTAG=v1.16.0
Generating semantic convention constants from specification version v1.16.0 at ../opentelemetry-specification
semconvgen -o semconv/v1.16.0 -t semconv/template.j2 -s v1.16.0 -i ../opentelemetry-specification/semantic_conventions/. --only=resource -p conventionType=resource -f generated_resource.go
panic: unable to render template: exit status 2
usage: gen-semconv [-h] [--debug]
                   [--only {span,resource,event,metric,units,scope}]
                   [--yaml-root folder] [--exclude EXCLUDE]
                   [YAML_FILE [YAML_FILE ...]] {code,markdown} ...
gen-semconv: error: No semantic convention model found!


goroutine 1 [running]:
main.main()
	/home/frzifus/git/go/observability/opentelemetry-go-build-tools/semconvgen/generator.go:62 +0x48e
make: *** [Makefile:290: gensemconv] Fehler 2

---

Details: #217 (comment)