Brant Evans

The logfile for rebuilding the remote container contains the line: ``` Start: Run: podman build -f /tmp/vsch/updateUID.Dockerfile-0.158.0 -t vsc--6b90a6b25fcf980178bfcceafb62a3c5-uid --build-arg BASE_IMAGE=vsc--6b90a6b25fcf980178bfcceafb62a3c5 --build-arg REMOTE_USER=vscode --build-arg NEW_UID=4400 --build-arg NEW_GID=4400 --build-arg IMAGE_USER=root /tmp/vsch...

I just had a chance to test this as well and adding the two lines that @tepene listed works for me too.

@sean-m-sullivan I'm reopening this issue as #343 did not fix this issue. I found this problem while fixing #343 so I opened the issue.

@djdanielsson Do you know if the current expected result is due to how the collection works or is an underlying issue with the awx.awx collection?

I don't know what the web UI does under the covers. A label only exists as long as it is attached to at least one JT or WFJT. Once the...

I took a look at the awx.awx collection [documentation for the job_template module](https://docs.ansible.com/ansible/latest/collections/awx/awx/job_template_module.html) which states the below regarding labels:  So in this collection for JTs and WFJTs we need...

We should at least document in the applicable roles Readme's that labels must be created prior to using and that the labels role can be used to create the labels.

If the playbooks are just examples then and not meant to be used OOTB directly running or importing the playbook then they shouldn't be in the `playbooks` directory. I think...

> I do think we need to update the roles readmes and test with up to date examples, Should that be the standard, No examples, but every role has a...

I agree with @djdanielsson about defaulting to 8 for now.