From 510d3c5fdc486e84d249bf395b4a862b4b9a3c00 Mon Sep 17 00:00:00 2001 From: Laurent Peuch Date: Sat, 11 Feb 2023 22:09:22 +0100 Subject: [PATCH 1/2] Add yet another warning message for when the container doesn't have access to the internet So people as dumb as me doesn't waist their time too. --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index d9e15eb..5ce672e 100644 --- a/README.md +++ b/README.md @@ -182,6 +182,8 @@ This should automatically download from `devbaseimgs.yunohost.org` a pre-build y After starting the LXC, your terminal will automatically be attached to it. If you later disconnect from the LXC, you can go back in with `./ynh-dev attach`. Later, you might want to destroy the LXC. You can do so with `./ynh-dev destroy`. +If you container **doesn't have an ip address nor access to internet**, this is likely because you either have a conflict with another virtualization system or that a program running on the host is using the port 53 and therefore prevent LXD's dnsmasq to run correctly (as stated before in the setup section.) + ## 3. Development and container testing After SSH-ing inside the container, you should notice that the *directory* `/ynh-dev` is a shared folder with your host. In particular, it contains the various git clones `yunohost`, `yunohost-admin` and so on - as well as the `./ynh-dev` script itself. From eca696cd9d510878148dfb663c02c05b7516bc7b Mon Sep 17 00:00:00 2001 From: Laurent Peuch Date: Sat, 11 Feb 2023 22:10:17 +0100 Subject: [PATCH 2/2] Remind the developper that they'll likely want to do a postinstall once in the container --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 5ce672e..58c02de 100644 --- a/README.md +++ b/README.md @@ -188,6 +188,8 @@ If you container **doesn't have an ip address nor access to internet**, this is After SSH-ing inside the container, you should notice that the *directory* `/ynh-dev` is a shared folder with your host. In particular, it contains the various git clones `yunohost`, `yunohost-admin` and so on - as well as the `./ynh-dev` script itself. +**Most of the time, the first thing you'll want to do is to start by running `yunohost tools postinstall` as the first command** (except if you are working on something that happens before the postinstall). + Inside the container, `./ynh-dev` can be used to link the git clones living in the host to the code being ran inside the container. For instance, after running: