ludeeus / integration_blueprint

Blueprint for custom_component developers.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Dont understand how to use the dev container

oncleben31 opened this issue · comments

I'm not sure to understand how to work with the dev container linked to the blueprint.

Version of the custom_component

Latest of the 25th April 2020

Configuration

N/A

Describe the bug

After creating a new github repo using blueprint as a template. I clone it locally on my Mac. I open the folder in dev container and I open a terminal. I tried the command dc init and got this.

container# dc init
/usr/bin/dc: line 6: /usr/share/container/*: No such file or directory
/usr/bin/dc: line 52: InitDevEnv: command not found
the 'dc' CLI is deprecated and will be removed in a future version, use 'cc' instead

So I have tried the cc init command with no more success:

container# cc init
cc: error: init: No such file or directory
cc: fatal error: no input files
compilation terminated.

I'm not sure if it's a bug or a wrong usage of the dev container.

Debug log

N/A

There was a namespace issue.
cc is renamed to container
Do a docker pull ludeeus/container:integration, then rebuild the container and it should works as intended,

init is not needed when you already have the file structure.
so a container start should be all you need.

I've tested your instructions. I have still errors with tasks:

> Executing task: dc check <

dc: can't open 'check': No such file or directory
Le processus du terminal s'est achevé avec le code de sortie 1

Le terminal sera réutilisé par les tâches, appuyez sur une touche pour le fermer.

> Executing task: dc set-version <

dc: can't open 'set-version': No such file or directory
Le processus du terminal s'est achevé avec le code de sortie 1

Le terminal sera réutilisé par les tâches, appuyez sur une touche pour le fermer.

How can I help you find the root cause ?

Cool it works.
As we are on the topic. In the main README.md file, it is written next to ./devcontainer/*:

Used for development/testing with VSCODE, more info in the readme file in that dir."

I understand I should find a readme file in .devcontainer folder explaining how to use the commands available. This file is missing.

We can close this issue with PR #26 merged.
Thank you for the support.