Glad you got it sorted. I understand there is some explanation of this in the welcome email you get when you register. Thanks
I don’t have enough trust to allow me to post the question that I want to and clicking around now and then for a few days has not given me what ever trust is needed. If there are more exact instructions in the welcome email I’d be grateful if you could post them here. I created my Ubuntu account a long time ago so didn’t get any welcome mail. I’m missing the old forum already.
Same for me, could you up my trust level?
I must say I’m quite surprised of the choice of Ubuntu to restrict that much the access for newcomers. Something I’ve never seen on any site, including professional ones.
If one comes to a product/company forum, it’s generally because he has some kind of issue with these products…
Regards
1 Like
Done. You should be able to post now
2 Likes
The reason for this is explained here FAQ: LXD has been moved to Canonical and we are in the process of working out a longer term solution that works well for all parties.
2 Likes
Same here. I’d like to ask a support question for LXD but can’t seem to find out how to post a new topic.
Hi, I bumped your trust level. The new user email you received when registering explained how to increase your trust level.
Hi. Just joined to ask where to find more information on the side effects.
I understand LXD is a frontend for several backends (from lxc to qemu). But what exactly are the side effects on commands such as lxc config device add container-name home disk ...
what will happen on lxc? on qemu? on a system-container? etc?
Do changing network options will only affect virtual network or firewall rules to my main networks (like docker does?)
Hi @gcb
The exact side effects depend on the device type that is being added, but essentially the command lxc config device add ... just attaches an existing device to the target instance.
Regarding the firewall, LXD adds the required firewall rules. Therefore, changing the network options will affect both network and firewall rules.
You might also see conflicts between the rules defined by your firewall (or another application) and the firewall rules that LXD adds. For example, your firewall might erase LXD rules if it is started after the LXD daemon, which might interrupt network connectivity to the instance.
Source: https://documentation.ubuntu.com/lxd/en/latest/howto/network_bridge_firewalld/
Can my trust level be bumped as well? New account, opened and read 5-10 topics, then checked the one email I received from Ubuntu, but don’t see anything related to a trust level (it instructs me how to validate my email address).
Thx!
1 Like
It looks like your trust level has been increased, can you post now?
@tomp this is probably getting old, but I just joined and don’t see instructions on the Ubuntu One email I received on increasing trust level. Can you boost my trust level? Thanks.
I too, have not received the upgraded trust level allowing me to post a topic. This must be specific to LXD, because I have posted on other Canonical topics.
I increased your trust level.
However, this is a new account - if you have posted before, it was with a different account.
Thank you. Interesting. It goes through my long time Ubuntu-One account. Apparently the Discourse is new. Very interesting.
This is ridiculous. Why is there a support-category in the first place if people aren’t allowed to post support requests?? It doesn’t serve anyone’s best interest for people to have to tack their questions to random existing threads!
I just wanted to post a question, because I cannot find an answer anywhere, but I apparently do not have the permission to do so! Canonical really went the whole wrong way about this migration, IMHO.
1 Like
I’ve increased your trust level.
The support category is a temporary workaround so that LXD support requests don’t show up on the main homepage of the Ubuntu forum.
The new user restrictions apply to all new users on the Ubuntu forum, but we are aware that it is problematic for users who just want to post a support request. Hopefully this is something that can be resolved in the future.