ennui
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Posts posted by ennui
-
-
Hello,
It looks like one of the machines hosting Funtoo containers has run out of space:# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdc1 466G 466G 68K 100% / [...]
-
12 hours ago, palica said:
rm -rf /var/git/meta-repo
ego sync
Yes, that fixes the issue. Thanks!
So no more Portage tree mapping into Funtoo containers? Then I believe "Why is my Portage tree read-only?" should be removed from the Funtoo Containers page. -
14 minutes ago, quantum said:
have you tried ?
ego sync# ego sync Syncing meta-repo ERROR: Meta-repo exists but does not appear to be a git repository. Can't sync.
Note that this question is specific to my Funtoo Container.
-
I recall the Portage tree meta repository was mounted into hosted containers (at /var/git) previously. However, it seems to have disappeared from mine. Is there something I need to do to bring this back? Should I make my own clone of the Portage tree into my container going forward?
-
9 minutes ago, palica said:
yes, apparmor was blocking dovecot.
Understood. Thanks for rectifying.
-
My container was rebooted on Apr 17 22:36 UTC. Previously, my dovecot installation was non-functional since the migration to LXD, as execv() calls to dovecot's helper processes were failing. Now, after this reboot, dovecot is working as expected again.
Was there a mandatory access control (MAC) or some other restriction mechanism in place on the host system? -
Reddit suits me fine. Will be interesting to see if it can drive a higher volume of discussion.
-
I see postfix-3.1.1-r1 came in from funtoo-staging. Thanks for that!
Is it possible to bring in iputils as well? I opened https://bugs.funtoo.org/browse/FL-3261to track.

2nd Generation Funtoo Compute Infrastructure and Plan Upgrades
in Funtoo Hosting
Posted
@palica @drobbins: Is AppArmor blocking Dovecot again? I see my Dovecot processes went down around 2019-11-18 01:35:01 UTC:
Subsequent attempts to restart Dovecot are failing: