>> (p.1)
    Author Topic: testnet4 in a SAFER container (bitcoin core, lightning core, ckpool, cpuminer)  (Read 190 times)
    mocacinno (OP)
    Legendary
    *
    Offline

    Activity: 4060
    Merit: 5541


    ♻️ Automatic Exchange


    View Profile WWW
    June 26, 2024, 07:52:27 AM
    Last edit: June 26, 2024, 08:41:42 AM by mocacinno
    Merited by ABCbits (9), champloo (2)
     #1

    This topic is replacing the (very cluttered) topic https://bt.irlbtc.com/view/5496494



    TL;DR; => Jump straight to your usecase
    i only want to run a node, maybe a wallet aswell
    i want to get involved by running a lightning node on  testnet4
    i want to run a solo mining pool on testnet4
    eventough it's not a good idear, i want to cpu mine on testnet4



    I got interested in testnet4, but at that time it was pretty hard for most people to run a node, let alone mine or open a lightning node on testnet4. That's why i decided to build a couple of containers based on ubuntu 24.04's image.

    The problem is/was that the official ubuntu 24.04 image already contains a bunch of vulnerability's, and we need to run the container in privileged mode...
    A second problem is/was that i decided to "combine" services into one container: "node + lightning", "node + cpuminer", "node + ckpool", "node + lighting + cpuminer + ckpool". This made the setup really hard to maintain.

    Instead of moving foreward in the direction i took, i decided to re-design the containers from the ground up, using the (much safer) minimal Base Container Images provided by SuSe and (if possible) separating the different services making them easyer to maintain. I compile the tools using the BCI-base image, then copy over library's and binary's into the BCI-minimal image... This way the attack vector is allmost completely gone (dockerhub's free scan tool no longer finds a single vulnerability in my new container images, but offcourse, nothing is absolute, so it's well possible undisclosed vulnerability's still exist).

    Because i did a complete re-design of the container images, i closed the old (cluttered) thread and started fresh.
    Notice for people running the "old" images: don't worry... It's not like the old images are unsafe to run... The vulnerability's found in ubuntu's 24.04 base image are present in allmost all containers you find on the internet. They'll probably be present on your "regular" OS or your webserver aswell. Running the images i previously created doesn't necessarily put you in harms way, you're probably just as secure as ~95% of the people out there... It's just that i want you to be MORE secure, so do consider moving to the new container images Smiley

    Want to have a visual representation of what i did... Just look here. The tags starting with bci_ are the new containers, the other ones are the "old" containers... You should immediately notice the "new" bci_ containers have the string "None found" under "vulnerability's", whilst the old ones have quite a few. You should also notice the "new" bci_ containers are much smaller (due to the fact only the strictly necessary components are included, making the attact surface as small as possible)

    ░░░░▄▄████████████▄
    ▄████████████████▀
    ▄████████████████▀▄█▄
    ▄██████▀▀░░▄███▀▄████▄
    ▄██████▀░░░▄███▀▀██████▄
    ██████▀░░▄████▄░░░▀██████
    ██████░░▀▀▀▀▄▄▄▄░░██████
    ██████▄░░░▀████▀░░▄██████
    ▀██████▄▄███▀░░░▄██████▀
    ▀████▀▄████░░▄▄███████▀
    ▀█▀▄████████████████▀
    ▄████████████████▀
    ▀████████████▀▀░░░░
     
     CCECASH 
     
        ANN THREAD    
     
          TUTORIAL      
Page 1
Viewing Page: 1