[00:00:42]
<Yunohost Git/Infra notifications> [doc.yunohost.org] yunohost-bot pushed 1 commit to master: docs: update tooltips ([518f925e](https://github.com/YunoHost/doc.yunohost.org/commit/518f925e243673d6a0b0be37a6502f4e77238ca5))
[00:02:03]
<Yunohost Git/Infra notifications> [doc.yunohost.org] yunohost-bot pushed 1 commit to master: docs: update tooltips ([fd6ec30f](https://github.com/YunoHost/doc.yunohost.org/commit/fd6ec30f2be55d1286d3f69fd0570406da4fc3d7))
[06:15:55]
<Yunohost Git/Infra notifications> [issues] OniriCorpe opened [issue #2382](https://github.com/YunoHost/issues/issues/2382): Do not start an upgraded app if its service was disabled
[06:15:56]
<Yunohost Git/Infra notifications> [issues] OniriCorpe labeled :package: App management on [issue #2382](https://github.com/YunoHost/issues/issues/2382): Do not start an upgraded app if its service was disabled
[06:15:57]
<Yunohost Git/Infra notifications> [issues] OniriCorpe labeled good first issue on [issue #2382](https://github.com/YunoHost/issues/issues/2382): Do not start an upgraded app if its service was disabled
[06:15:59]
<Yunohost Git/Infra notifications> [issues] OniriCorpe labeled :space_invader: bug on [issue #2382](https://github.com/YunoHost/issues/issues/2382): Do not start an upgraded app if its service was disabled
[17:38:08]
<stan> Hello,
I am currently trying to set up the environment development with incus. Incus installation is ok. I run `./ynh-dev start`, the image is downloaded and I start the postinstall. I chose a domain, a name and a password but then I get a warning telling me there is Connection time out. This provokes an error saying 'Unable to set new hostname'
And I get this 3 times in a row, the aliases are created and fially updating the application catalog fails as well. It seems that the connection to yunohost.org fails
Here are the logs https://paste.yunohost.org/ehupudigog.kotlin
The documentation in github says
> 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 Incus's dnsmasq to run correctly (as stated before in the setup section.)
I checked the ports used by my VM (debian 12) and it appears that the port 53 is only used by incus 🤔
Any idea to help me?
[17:39:02]
<Aleks (he/him/il/lui)> hmmm sounds like the container doesn't have internet ?
[17:39:08]
<Aleks (he/him/il/lui)> are you able to ping any external ip ?
[17:42:40]
<stan> ouch
Temporary failure in name resolution
[17:43:16]
<Aleks (he/him/il/lui)> yeah but what about any ip
[17:43:23]
<Aleks (he/him/il/lui)> eg `ping 8.8.8.8`
[17:43:45]
<stan> ok this works
[17:44:54]
<Aleks (he/him/il/lui)> ah interesting
[17:45:03]
<Aleks (he/him/il/lui)> well let's look at what's the resolver in /etc/resolv.conf then
[17:45:27]
<Aleks (he/him/il/lui)> i guess a naive quickfix can be to `rm /etc/resolv.conf` and `echo 'nameserver 8.8.8.8' > /etc/resolv.conf`
[17:46:14]
<stan> at the moment I just have `nameserver 127.0.0.1`
[17:46:18]
<stan> I'll try your commands
[17:46:51]
<Aleks (he/him/il/lui)> hmyeah so maybe the source of the issue is that dnsmasq is down maybe ? what does `systemctl status dnsmasq` yields ?
[17:47:13]
<stan> no it is active
[17:48:00]
<stan> but it also yields `no servers found in /run/dnsmasq/resolv.conf, will retry`
[17:48:35]
<Aleks (he/him/il/lui)> hmmmokay
[17:48:48]
<Aleks (he/him/il/lui)> well it's supposed to use /etc/resolv.dnsmasq.conf if i remember correctly
[17:49:31]
<Aleks (he/him/il/lui)> but anyway i wouldnt mind too much about it, just rm and `echo 'nameserver 8.8.8.8' > /etc/resolv.conf` should do the trick
[17:51:19]
<stan> same behaviour
[17:55:27]
<stan> And destroying and starting again the container does not change anything
[17:58:30]
<stan> I don't know why but now the postinstall works
Thanks @Aleks
[17:58:46]
<Aleks (he/him/il/lui)> by "same behavior", do you mean you still can't resolve domain names after changing the resolv.conf ?
[17:58:50]
<Aleks (he/him/il/lui)> ah 🤔
[20:45:30]
<Yunohost Git/Infra notifications> 🏗️ Starting build for metronome/4.0.3.1+ynh12 for bookworm/unstable/i386 ...
[20:48:09]
<Yunohost Git/Infra notifications> ✔️ Completed build for metronome/4.0.3.1+ynh12 for bookworm/unstable/i386.
[20:48:14]
<Yunohost Git/Infra notifications> 🏗️ Starting build for metronome/4.0.3.1+ynh12 for bookworm/unstable/amd64 ...
[20:49:20]
<Yunohost Git/Infra notifications> ✔️ Completed build for metronome/4.0.3.1+ynh12 for bookworm/unstable/amd64.
[20:49:29]
<Yunohost Git/Infra notifications> 🏗️ Starting build for metronome/4.0.3.1+ynh12 for bookworm/unstable/armel ...
[20:51:23]
<Yunohost Git/Infra notifications> ❌ Failed to include change of metronome/4.0.3.1+ynh12 for bookworm/unstable/armel ?!
[20:51:27]
<Yunohost Git/Infra notifications> 🏗️ Starting build for metronome/4.0.3.1+ynh12 for bookworm/unstable/armhf ...
[20:52:04]
<Yunohost Git/Infra notifications> ❌ Failed build for metronome/4.0.3.1+ynh12 for bookworm/unstable/armhf ?!