Flo
Flo
A simple "stat" on the source would be enough. Does it exist? Great. If not, is it optional? Great, not adding that one to the run command. Not optional? Here,...
The use case is: Mounting configuration files from the host system. The recommended way to do that is using bind mounts (see your link). It's not about copying config files...
> and optional because the default value works anywhere. Except for Codespaces, K8s and other "locked" systems where you can't create a configuration file. Also it's not very user friendly....
It's useless to discuss with you as long as you only accept your own opinion. I'm out of here.
I can also confirm this issue, and I can offer another workaround: Putting the language string into quotes also helps.
I'm sorry to disappoint you, but ansible-lint is present and works. The error message is caused when the file checked by ansible-lint does not contain valid yaml. Edit; ```text Command...
 This is a vscode devcontainer. Non-root, no virtualenv. `requirements.txt` - stripped. Container simply runs `pip3 install --user -r requirements.txt` after creation. ```text ansible==4.4.0 Jinja2>=2.11.2 netaddr PyYAML==5.3.1 molecule ansible-lint pycodestyle==2.9.1...
Hey @priyamsahoo, thank you for looking into this! You're probably right, something doesn't work here. Even after setting the path for ansible-lint, the extension is unable to get the information....
Hello @priyamsahoo A quick update: `v0.14.73` obviously solved the issue of not recognizing the ansible-lint binary. ```jsonc [Trace - 11:26:16 AM] Received notification 'update/ansible-metadata'. Params: [ [ { "ansible information":...
@ganeshrn I'm sorry, I can't test 😢 