As it is hosting all my websites I don't really want to take it down to do a fresh install.
Not even sure how to do that on a container?

 

All containers now have private meta-repos now. If you previously had a shared meta-repo, you can fix meta-repo by performing the following steps:

# rm -rf /var/git/meta-repo
# ego sync

Then run ego sync to update your meta-repo as needed. Note that 1.2 is no longer receiving updates and many of you need to upgrade to 1.3. I can assist by loading up a new 1.3 container for you to migrate to -- email me if you are interested in this.

?

Thanks!

Thoughts?

We have deployed our second-generation compute infrastructure and have begun the process of moving containers over to it. This funtoo-based infrastructure is running on faster hardware and is using ZFS for storage. For more information on our second-generation platform, see https://www.funtoo.org/Funtoo_Containers

Also note that plans have been upgraded. Our base plan for $15/mo now comes with 8 cores and 60GB of storage (was 6 cores and 50GB previously.) The medium plan now has 16 cores and 120GB of storage (was 12 cores and 100GB). And our large plan now has 32 cores and 240GB of storage (was 24 cores and 200 GB). All existing containers will be automatically upgraded to these new resource levels when they are migrated to the new infrastructure :)

Best,

Daniel

# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdc1       466G  466G   68K 100% /
[...]

Jul 21 00:19:58 dkg agetty[5782]: /dev/tty1: cannot open as standard input: No such file or directory                                                                                  
Jul 21 00:19:58 dkg agetty[5784]: /dev/tty3: cannot open as standard input: No such file or directory                                                                                  
Jul 21 00:19:58 dkg agetty[5786]: /dev/tty5: cannot open as standard input: No such file or directory                                                                                  
Jul 21 00:19:58 dkg agetty[5787]: /dev/tty6: cannot open as standard input: No such file or directory                                                                                  
Jul 21 00:19:58 dkg agetty[5783]: /dev/tty2: cannot open as standard input: No such file or directory                                                                                  
Jul 21 00:19:58 dkg agetty[5785]: /dev/tty4: cannot open as standard input: No such file or directory

Which is true, those devices do not exist.  And it makes sense that a container isn't going to have all these ttys, either.  I just don't know how to tell it not to look for them.

Thanks.

I'm searching for sponsored vps that builds unofficial funtoo iso images with my script. Anyone can provide?:

• It uses linux-live script from Tomas M to boot the sqaushed filesystem.
• It uses 2 installer:
  • created by me (from terminal use "install-funtoo")
  • Calamares (thanks to@Otakku for providing scripts)

Question for @drobbins: Can you approve my project that would be official?

Greetings Daniel K.

I am currently renting out a large sized funtoo container and started up a small jenkins instance (it's got one job) on there. The issue is that I am consistently seeing it crash with the errors:

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0x00007fd18b2cb8be, pid=11645, tid=0x00007fd173a51700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_192-b12) (build 1.8.0_192-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.192-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x9578be]  PerfLongVariant::sample()+0x1e

Google research is showing that it's an issue with the memory or diskspace, but I have the jvm tmp directory in a user home folder and there's still 137G available space on there

Has anyone encountered this issue or know how to deal with this when running in a funtoo container? I'm running the process with the below command:
java -server -Djava.io.tmpdir=/home/user/jenkins/tmp -Xms40966m -Xmx8192m -jar jenkins.war 

Uploaded hs_err_pid11645.log

just curious. :)

What are the reason(s) that kernel for *.hots.funtoo.org has been switched (downgraded) from 4.14 to 4.9?

Thanks,

--

Saulius

As we move to our third-generation infrastructure, I am currently migrating containers to BTRFS+SSD (from ZFS and HDD+Optane) which may result in up to an hour of downtime, especially if you have a lot of data stored in your containers. But the result will be much, much, much faster IO. So if you have seen your uptime on your container change recently, this is why.

Best,

Daniel

Progress on this is going well. All of Funtoo (www, forums, bugs, auth) is now hosted on this brand-new infrastructure and performance of all the funtoo sites now appears to be very very good. We did initially have some issues we were experiencing with ZFS so we are now using another approach which will be detailed in future docs, and it is running much better.

Soon, we will be launching new things related to funtoo hosting in regards to the new infrastructure. Much more automation, rather than having to send us an email to get things done. Some surprises -- and that's one of the reasons why we added authy integration to the funtoo logins -- because they will be used to manage your containers in the future so we want to have more sophisticated security capabilities.

Best,

Daniel

Since earlier this year I work for a thrift shop-chain. Part of my job (for 2 days/week) is running the PC refurbishment project. When I first joined this project Linux Mint was used to install a new OS on refurbished computers. Trust me, systemd on a P4 is a disaster. But who wants systemd anyway ;)  So after a while I came across some nice professional network hardware (Gbit managed switches, several) and using an Intel Core 2 machine I created a local network w/o internet access. I also took the decision to change the OS to Devuan Linux with the MATE DE, as the intended audience/user-base are novice Linux users. To this aim I maintain a local repo of Devuan, updated weekly via a portable HDD drive. In the near future a new fiber-optic internet connection will be activated, but as its speed cannot match what I have now to transfer large chunks of data (sorry, packages ;) ) I'll keep the local repo in use for the time being. But the updating process will need some overhauling, having to log around with heavy USB drives is getting quite tedious now.

So, with the upcoming access to high-speed internet I've obtained permission to connect to the to-be-launched wifi network during the night to update said repo. But I also would like to have a local Funtoo repo on the same machine, equally updated during the night. This means I need at least 2 virtual machines and from reading my way around, it seems Linux Containers may do what I want: run a Funtoo base system, with a pair for virtual machines on top, one running Funtoo and the other Devuan, each updating itself during the night before switching off again. (I'll be writing some scripts for that, but first getting to grips with LXC!) Is this possible, how do I proceed (the replacement server already has a fresh Funtoo 1.2 install on it) and how do I create my own containers as I'm aware there's nothing for Devuan nor the Core2 metal the server runs on (Funtoo only supports Westmere so far, by the looks of it).

TIA!

emerge -auND --with-deps=y @world

and rebooting. Five packages ware updated (vim + some others). And now ssh root@xxx.host.funtoo.org prints banner and returns with “Connection to xxx.host.funtoo.org closed.” and exit code 254. I tried to use some options like “--noprofile bash”, “--noprofile sh” , “-t” but without any result. Also, I tried to get any file via scp with

scp root@xxx.host.funtoo.org:/etc/ssh/sshd_config ./

but error “protocol error: unexpected <newline>” is returned. Logs of ssh with -vv flag is attached.

log.txt

If anyone needs their container to be wiped and reloaded to a fresh 1.2 installation, please email us at support@funtoo.org and let us know.

Best,

Daniel

I don't know if it is related, but I recently switched epro build from stable to current (I was with ego-2.3.0 I think) and that broke my epro/ego/emerge somewhat. I had hard time to have all them back on track...

# eix-update  
Reading Portage settings... 
Building database (/var/cache/eix/portage.eix)... 
cannot open /usr/portage/profiles/categories: No such file or directory 
[0] "" /usr/portage/ (cache: metadata-md5-or-flat) 
     Reading category 0|0 (100) EMPTY! 
Applying masks... 
Calculating hash tables...

# ll /usr
lrwxrwxrwx   1 root root   18 Nov 29  2016 portage -> ../var/src/portage (broken symlink, I removed it)


# cat /etc/ego.conf 
[global] 
meta_repo_path = /var/git/local/meta-repo 
release = 1.2

Any idea ?

A large number of home routers are vulnerable to malware and can be used to scrape your passwords and other important data. Please take a look at https://blog.talosintelligence.com/2018/06/vpnfilter-update.html -- specifically the "Known affected devices" part -- and see if your router has an exploitable security hole. Affected devices listed below....

Given our observations with this threat, we assess that this list may still be incomplete and other devices may be affected.

ASUS DEVICES:
RT-AC66U (new)
RT-N10 (new)
RT-N10E (new)
RT-N10U (new)
RT-N56U (new)
RT-N66U (new)

D-LINK DEVICES:
DES-1210-08P (new)
DIR-300 (new)
DIR-300A (new)
DSR-250N (new)
DSR-500N (new)
DSR-1000 (new)
DSR-1000N (new)

HUAWEI DEVICES:
HG8245 (new)

LINKSYS DEVICES:
E1200
E2500
E3000 (new)
E3200 (new)
E4200 (new)
RV082 (new)
WRVS4400N

MIKROTIK DEVICES:
CCR1009 (new)
CCR1016
CCR1036
CCR1072
CRS109 (new)
CRS112 (new)
CRS125 (new)
RB411 (new)
RB450 (new)
RB750 (new)
RB911 (new)
RB921 (new)
RB941 (new)
RB951 (new)
RB952 (new)
RB960 (new)
RB962 (new)
RB1100 (new)
RB1200 (new)
RB2011 (new)
RB3011 (new)
RB Groove (new)
RB Omnitik (new)
STX5 (new)



NETGEAR DEVICES:
DG834 (new)
DGN1000 (new)
DGN2200
DGN3500 (new)
FVS318N (new)
MBRN3000 (new)
R6400
R7000
R8000
WNR1000
WNR2000
WNR2200 (new)
WNR4000 (new)
WNDR3700 (new)
WNDR4000 (new)
WNDR4300 (new)
WNDR4300-TN (new)
UTM50 (new)

QNAP DEVICES:
TS251
TS439 Pro
Other QNAP NAS devices running QTS software

TP-LINK DEVICES:
R600VPN
TL-WR741ND (new)
TL-WR841N (new)

UBIQUITI DEVICES:
NSM2 (new)
PBE M5 (new)

UPVEL DEVICES:
Unknown Models* (new)

ZTE DEVICES:
ZXHN H108N (new)

* Malware targeting Upvel as a vendor has been discovered, but we are unable to determine which specific device it is targeting.

Thanks!

PS: move pls to Funtoo Hosting forum.

reboot

or

shutdown

has no effect

Firewall:

1.  An internet presence without a firewall encourages abuse and is a poor practice that contributes to the harm of the internet and its users. 

2.  Firewalls can and should be used as a learning tool to help grow the understanding of Funtoo and Linux in general.  learning firewall implementation makes for a better user.

3.  iptables provides a wealth of other neat tools to help users learn basics and advanced concepts of networking such as masquerade and DPI. 

4.  the consequences of a breech far outweigh the repercussions of expanded conntrack overhead, whatever it may be.  a compromised container can put funtoo in RBL territory and reputation system blacklists.  our users deserve firewalls and freedom from the 'one rotten egg' type of bans on subnets enforced by google and cisco.

5.  its FUN to play in iptables http://shortround.net/2010/09/24/making-an-image-flip-proxy/

IPv6: 

1.  "Do IT" --S. LeBouf.

2.  ARIN insisted we have our collective ducks in a row in 2012.   Its had meaningful support in the kernel since 2006.  its support at the carrier level is ubiquitous.  most ISP's offer a v6 address, if not a subnet, for the user.

3.  nearly every hosting provider on earth supplies a v6 subnet to their customer.   If we continue treating IPv6 as an option and subject to interest, we tacitly imply a shortcoming in Funtoo. 

4.  ipv6 ipsec extensions are the security we need in 2016. modular headers, ndp, stateless and stateful configuration and host based routing isnt something thats going away.

5.  even your cellphone uses IPv6.  if you're a T-Mobile subscriber your stack to the tower is almost entirely v6.

6.  its fun to play with new things.  ipv6 load balancing is super neat.  developing new software that uses ipv6 means your container will have to support ipv6.

for containers to be competitive, attractive and useful, it means they have to support things that every other container supports.

What is the recommended way to use overlay on a funtoo container ?