ProHoster > Блог > Maamulka > Sida loo bilaabo isticmaalka Habka Isticmaalaha gudaha Linux

Sida loo bilaabo isticmaalka Habka Isticmaalaha gudaha Linux

Horudhac ka yimid turjubaanka: Marka laga soo horjeedo soo galitaanka ballaaran ee nolosheena ee noocyada kala duwan ee weelasha, waxay noqon kartaa mid aad u xiiso badan oo faa'iido leh in la ogaado teknoolojiyadda ay dhammaantood bilaabeen hal mar. Qaar ka mid ah ayaa si faa'iido leh loo isticmaali karaa ilaa maantadan la joogo, laakiin qof kastaa ma xasuusan karo hababkan oo kale (ama garanayo haddii aan la qaban inta lagu jiro horumarkooda degdegga ah). Mid ka mid ah tignoolajiyada noocaas ah waa Isticmaalka Mode Linux. Qoraaga asalka ah wuxuu sameeyay wax badan oo qodis ah, isaga oo ogaanaya mid ka mid ah horumarkii hore ee wali shaqeeya iyo kuwa aan shaqeynin, wuxuuna isu geeyay wax la mid ah tilmaamo tallaabo-tallaabo ah oo ku saabsan sidii aad naftaada u heli lahayd UML-guri ee 2k19. Haa, waxaanu ku martiqaadnay qoraaga boostada asalka ah Habr Cadeey, markaa haddii aad wax su'aalo ah qabtid - ku weydii Ingiriis faallooyinka.

Sida loo bilaabo isticmaalka Habka Isticmaalaha gudaha Linux

Habka isticmaale ee Linux waa, runtii, deked Linux kernel lafteeda. Habkani wuxuu kuu ogolaanayaa inaad ku socodsiiso kernel buuxa Linux sida habka isticmaale waxaana badanaa isticmaala horumariyayaashu si ay u tijaabiyaan darawalada. Laakiin qaabkani sidoo kale waa mid faa'iido leh sida qalab go'doomin guud, mabda'a kaas oo la mid ah hawlgalka mashiinnada farsamada. Habkani wuxuu bixiyaa go'doon ka badan Docker, laakiin in ka yar mashiinka farsamada ee buuxa sida KVM ama Virtual Box.

Guud ahaan, Habka Isticmaaluhu wuxuu u ekaan karaa qalab la yaab leh oo adag in la isticmaalo, laakiin wali wuxuu leeyahay isticmaalkiisa. Ka dib oo dhan, kani waa kernel Linux buuxa oo ka socda isticmaale aan mudnayn. Habkani wuxuu u oggolaanayaa kood aan la aamini karin inuu shaqeeyo iyada oo aan wax khatar ah ku dhicin mishiinka martida loo yahay. Oo maadaama tani ay tahay kernel buuxa, geeddi-socodyadeedu waxay ka go'an yihiin mashiinka martida loo yahay, taas oo ah Nidaamyada ka dhex socda Habka Isticmaaluhu ma arki doonaan martida loo yahay. Tani maaha sida weelka caadiga ah ee Docker, taas oo ay dhacdo mashiinka martida loo yahay had iyo jeer arko hababka gudaha kaydka. Ka fiirso qaybtan pstree ee mid ka mid ah adeegayaashayda: 

containerd─┬─containerd-shim─┬─tini─┬─dnsd───19*[{dnsd}]
           │                 │      └─s6-svscan───s6-supervise
           │                 └─10*[{containerd-shim}]
           ├─containerd-shim─┬─tini─┬─aerial───21*[{aerial}]
           │                 │      └─s6-svscan───s6-supervise
           │                 └─10*[{containerd-shim}]
           ├─containerd-shim─┬─tini─┬─s6-svscan───s6-supervise
           │                 │      └─surl
           │                 └─9*[{containerd-shim}]
           ├─containerd-shim─┬─tini─┬─h───13*[{h}]
           │                 │      └─s6-svscan───s6-supervise
           │                 └─10*[{containerd-shim}]
           ├─containerd-shim─┬─goproxy───14*[{goproxy}]
           │                 └─9*[{containerd-shim}]
           └─32*[{containerd}]

Oo tan barbar dhig pstree ee kernel Linux ee Habka Isticmaalaha:

linux─┬─5*[linux]
      └─slirp

Markaad la shaqeyneyso weelasha Docker, waxaan ka arki karaa martida loo yahay magacyada hababka ka dhex socda martida. Habka Isticmaalaha Linux, tani macquul maaha. Waxa loola jeedaa? Tani waxay ka dhigan tahay qalabka la socodka ee dhex mara nidaamka hoose ee xisaabinta ee Linux ma aragto hababka ku socda nidaamka martida. Laakiin xaaladaha qaarkood, qaabkani wuxuu noqon karaa seef laba af leh.

Guud ahaan, dhammaan boostada hoose waa ururinta cilmi-baarista iyo isku dayga adag si loo gaaro natiijada la rabo. Si tan loo sameeyo, waa inaan isticmaalo qalabyo qadiimi ah oo kala duwan, akhriya ilaha kernel-ka, sameeyaa sixid degdeg ah oo kood ah oo la qoray maalmihii aan weli ku jiray dugsiga hoose, iyo sidoo kale tinker la Heroku waxay dhistaa iyadoo la adeegsanayo binary gaar ah si aan u helo qalabka aan u baahanahay. . Shaqadan oo dhami waxay keentay nimankii IRC-ga ku jiray inay iigu yeedhaan sixir. Waxaan rajeynayaa in boostadani ay u adeegto sida dukumeenti la isku halleyn karo qof si uu isku dayo wax la mid ah kernels cusub iyo noocyada OS.

sixitaanka

Dejinta Habka Isticmaalaha Linux waxaa lagu sameeyaa dhowr tillaabo:

  • ku-tiirsanaanta ku-tiirsanaanta martigeliyaha;
  • soo dejinta kernel Linux;
  • qaabeynta kernel-ka;
  • fadhiga kernel;
  • rakibaadda binary;
  • habaynta nidaamka faylka martida;
  • xulashada xuduudaha bilaabista kernel;
  • dejinta shabakada martida;
  • bilaabista kernelka martida.

Waxaan u maleynayaa in haddii aad go'aansato inaad adigu sameyso, waxaad u badan tahay inaad sameyso wax kasta oo lagu sharraxay qaar ka mid ah Ubuntu ama nidaamka Debian-sida. Waxaan isku dayay inaan ka hirgeliyo dhammaan kuwa kor ku xusan qaybinta aan jeclahay - Alpine, laakiin waxba kama soo bixin, sida muuqata sababtoo ah xaqiiqda ah in kernel Linux uu leeyahay glibc-isms adag oo adag oo loogu talagalay darawalada Habka Isticmaalaha. Waxa aan qorshaynayaa in aan tan u soo sheego korka ka dib marka aan ugu dambeyntii fahmo dhibaatada.

Ku-tiirsanaanta ku-tiirsanaanta martigeliyaha

Ubuntu wuxuu u baahan yahay ugu yaraan xirmooyinka soo socda si loo dhiso kernel Linux (iyaga oo u maleynaya in rakibid nadiif ah):

- 'build-essential'
- 'flex'
- 'bison'
- 'xz-utils'
- 'wget'
- 'ca-certificates'
- 'bc'
- 'linux-headers'

Waxaad ku rakibi kartaa amarkan soo socda (sida xidid ama sudo):

apt-get -y install build-essential flex bison xz-utils wget ca-certificates bc 
                   linux-headers-$(uname -r)

Ogsoonow in socodsiinta barnaamijka dejinta kernel menu ee Linux ay u baahan doonto rakibaadda libncurses-dev. Fadlan hubi in lagu rakibay amarka soo socda (sida xidid ama sudo):

apt-get -y install libncurses-dev

Kernel soo dejiso

Go'aanso meesha aad ka soo dejisanayso ka dibna dhis kernel-ka. Hawlgalkan, waxaad u baahan doontaa inaad u qoondayso qiyaastii 1,3 GB oo meel disk ah, markaa iska hubi inaad haysato.

Kadib tag kernel.org oo hel URL si aad u soo dejiso kernelkii ugu dambeeyay ee xasilloon. Waqtiga qorista tani waa: https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.1.16.tar.xz

Soo deji faylkan adiga oo isticmaalaya 'wget':

wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.1.16.tar.xz

Oo la soo saar 'tar':

tar xJf linux-5.1.16.tar.xz

Hadda waxaan galeynaa hagaha la sameeyay markii la furayay kubbadda daamurka:

cd linux-5.1.16

dejinta Kernel-ka

Habka dhisidda kernel waa go'an Makefiles с badan qalabyada gaarka ah iyo qoraallada si loo toosiyo habka. Marka hore, fur barnaamijka dejinta isdhexgalka:

make ARCH=um menuconfig

Waxay qayb ahaan kuu dhisi doontaa oo kuu soo bandhigi doontaa sanduuqa wada-hadalka. Goorma '[Select]', waxaad awood u yeelan doontaa inaad isku hagaajiso adigoo isticmaalaya Space ama Geli furayaasha. Ku dhex soco daaqadda, sida caadiga ah, adigoo wata fallaadhaha kiiboodhka "kor" iyo "hoos", oo dooro walxaha - "bidix" ama "midig".

Tilmaamaha aragtida -> macnaheedu waa inaad ku jirto liiska hoosaadka, oo lagu galo adigoo riixaya furaha Gelida. Waddada looga bixi karo waa iska cad '[Exit]'.

Ku dar xulashooyinka soo socda '[Select]' oo hubi inay ku xigaan '[*]':

UML-specific Options:
  - Host filesystem
Networking support (enable this to get the submenu to show up):
  - Networking options:
    - TCP/IP Networking
UML Network devices:
  - Virtual network device
  - SLiRP transport

Taasi waa, waxaad ka bixi kartaa daaqadan adiga oo si isdaba joog ah u dooranaya '[Exit]'. Kaliya iska hubi in lagugu soo jeediyay inaad kaydiso qaabaynta dhamaadka oo dooro '[Yes]'.

Waxaan kugula talinayaa inaad la ciyaarto xulashooyinka kernel-ka ka dib markaad akhrido qoraalkan. Tijaabooyinkan, waxaad wax badan ka baran kartaa xagga fahamka shaqada makaanikada kernel-ka hooseeya iyo saameynta calannada kala duwan ay ku leeyihiin kulankooda.

Dhisida kernel-ka

Kernel-ka Linux waa barnaamij weyn oo sameeya waxyaabo badan. Xataa iyada oo la adeegsanayo qaabaynta ugu yar ee qalabkii hore, waxay qaadan kartaa wakhti in la dhiso. Markaa ku dhis kernel amarka soo socda:

make ARCH=um -j$(nproc)

Maxay? Amarkani wuxuu u sheegi doonaa wax-dhisahayaga inuu isticmaalo dhammaan xudunta CPU-ga iyo dunta la heli karo ee habka dhismaha. Kooxda $(nproc) dhamaadka Dhismuhu wuxuu bedelayaa wax soo saarka amarka nproc, taas oo qayb ka ah coreutils ku dhis Ubuntu caadiga ah.

Muddo ka dib, kernel-kayaga waxa lagu ururin doonaa fayl la fulin karo ./linux.

Ku rakibida binary-ga

Maadaama Habka Isticmaalaha ee Linux uu abuurayo binary caadi ah, waxaad u rakibi kartaa sida adeeg kasta oo kale. Waa kan sidaan u sameeyay:

mkdir -p ~/bin
cp linux ~/bin/linux

Waxa kale oo mudan in la hubiyo taas ~/bin ayaa kugu jirta $PATH:

export PATH=$PATH:$HOME/bin

Dejinta nidaamka faylka martida

U samee hagaha nidaamka faylka martida:

mkdir -p $HOME/prefix/uml-demo
cd $HOME/prefix

Fur alpinelinux.org iyo gudaha qaybta download hel link-ga soo dejinta dhabta ah MINI ROOT FILESYSTEM. Waqtiga qorista tani waxay ahayd:

http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-minirootfs-3.10.0-x86_64.tar.gz

Soo deji tarball-kan adigoo isticmaalaya wget:

wget -O alpine-rootfs.tgz http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-minirootfs-3.10.0-x86_64.tar.gz

Hadda geli tusaha nidaamka faylka martida oo soo saar kaydka:

cd uml-demo
tar xf ../alpine-rootfs.tgz

Ficilada la sharraxay waxay abuuri doonaan template nidaamka faylka yar. Dabeecadda nidaamka awgeed, aad bay u adkaan doontaa in baakooyinka lagu rakibo maamulaha apk Alpine. Laakiin FS-dan ayaa ku filnaan doonta inay qiimeeyaan fikradda guud.

Waxaan sidoo kale u baahanahay qalab tini si loo xakameeyo isticmaalka xusuusta hababka zombie kernel martidayada. 

wget -O tini https://github.com/krallin/tini/releases/download/v0.18.0/tini-static
chmod +x tini

Abuuritaanka khadka taliska kernel

Kernel-ka Linux, sida inta badan barnaamijyada kale, ayaa leh doodaha khadka-taliyaha ah ee lagu geli karo iyadoo la cayimayo furaha --help.

Laftiisa -caawin

linux --help
User Mode Linux v5.1.16
        available at http://user-mode-linux.sourceforge.net/

--showconfig
    Prints the config file that this UML binary was generated from.

iomem=<name>,<file>
    Configure <file> as an IO memory region named <name>.

mem=<Amount of desired ram>
    This controls how much "physical" memory the kernel allocates
    for the system. The size is specified as a number followed by
    one of 'k', 'K', 'm', 'M', which have the obvious meanings.
    This is not related to the amount of memory in the host.  It can
    be more, and the excess, if it's ever used, will just be swapped out.
        Example: mem=64M

--help
    Prints this message.

debug
    this flag is not needed to run gdb on UML in skas mode

root=<file containing the root fs>
    This is actually used by the generic kernel in exactly the same
    way as in any other kernel. If you configure a number of block
    devices and want to boot off something other than ubd0, you
    would use something like:
        root=/dev/ubd5

--version
    Prints the version number of the kernel.

umid=<name>
    This is used to assign a unique identity to this UML machine and
    is used for naming the pid file and management console socket.

con[0-9]*=<channel description>
    Attach a console or serial line to a host channel.  See
    http://user-mode-linux.sourceforge.net/old/input.html for a complete
    description of this switch.

eth[0-9]+=<transport>,<options>
    Configure a network device.
    
aio=2.4
    This is used to force UML to use 2.4-style AIO even when 2.6 AIO is
    available.  2.4 AIO is a single thread that handles one request at a
    time, synchronously.  2.6 AIO is a thread which uses the 2.6 AIO
    interface to handle an arbitrary number of pending requests.  2.6 AIO
    is not available in tt mode, on 2.4 hosts, or when UML is built with
    /usr/include/linux/aio_abi.h not available.  Many distributions don't
    include aio_abi.h, so you will need to copy it from a kernel tree to
    your /usr/include/linux in order to build an AIO-capable UML

nosysemu
    Turns off syscall emulation patch for ptrace (SYSEMU).
    SYSEMU is a performance-patch introduced by Laurent Vivier. It changes
    behaviour of ptrace() and helps reduce host context switch rates.
    To make it work, you need a kernel patch for your host, too.
    See http://perso.wanadoo.fr/laurent.vivier/UML/ for further
    information.

uml_dir=<directory>
    The location to place the pid and umid files.

quiet
    Turns off information messages during boot.

hostfs=<root dir>,<flags>,...
    This is used to set hostfs parameters.  The root directory argument
    is used to confine all hostfs mounts to within the specified directory
    tree on the host.  If this isn't specified, then a user inside UML can
    mount anything on the host that's accessible to the user that's running
    it.
    The only flag currently supported is 'append', which specifies that all
    files opened by hostfs will be opened in append mode.

Guddigani waxa uu muujinayaa halbeegyada ugu muhiimsan ee furitaanka. Aynu ku wadno kernel-ka xulashada ugu yar ee loo baahan yahay:

linux 
  root=/dev/root 
  rootfstype=hostfs 
  rootflags=$HOME/prefix/uml-demo 
  rw 
  mem=64M 
  init=/bin/sh

Sadarrada kore waxay noo sheegaan kernel-kayaga soo socda:

  • Ka soo qaad nidaamka faylalka xididku inuu yahay aalad been abuur ah /dev/root.
  • Dooro martigaliyayaasha sida darawalka faylalka xididka.
  • Ku dheji nidaamka faylka martida ee aan ku abuurnay aaladda xididka.
  • Iyo haa, habka wax-akhriska.
  • Isticmaal kaliya 64 MB ee RAM (waxaad isticmaali kartaa wax aad uga yar iyadoo ku xiran waxaad qorsheyneyso inaad sameyso, laakiin 64 MB waxay u egtahay qadarka ugu fiican).
  • Kernelku si toos ah ayuu u bilaabmaa /bin/sh sida init- geeddi-socod.

Orod amarkan oo waa inaad heshaa wax la mid ah kuwan:

Hal xaashi kale

Core dump limits :
        soft - 0
        hard - NONE
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking environment variables for a tempdir...none found
Checking if /dev/shm is on tmpfs...OK
Checking PROT_EXEC mmap in /dev/shm...OK
Adding 32137216 bytes to physical memory to account for exec-shield gap
Linux version 5.1.16 (cadey@kahless) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #30 Sun Jul 7 18:57:19 UTC 2019
Built 1 zonelists, mobility grouping on.  Total pages: 23898
Kernel command line: root=/dev/root rootflags=/home/cadey/dl/uml/alpine rootfstype=hostfs rw mem=64M init=/bin/sh
Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Memory: 59584K/96920K available (2692K kernel code, 708K rwdata, 588K rodata, 104K init, 244K bss, 37336K reserved, 0K cma-reserved)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS: 15
clocksource: timer: mask: 0xffffffffffffffff max_cycles: 0x1cd42e205, max_idle_ns: 881590404426 ns
Calibrating delay loop... 7479.29 BogoMIPS (lpj=37396480)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 512 (order: 0, 4096 bytes)
Checking that host ptys support output SIGIO...Yes
Checking that host ptys support SIGIO on close...No, enabling workaround
devtmpfs: initialized
random: get_random_bytes called from setup_net+0x48/0x1e0 with crng_init=0
Using 2.6 host AIO
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: 0, 6144 bytes)
NET: Registered protocol family 16
clocksource: Switched to clocksource timer
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
console [stderr0] disabled
mconsole (version 2) initialized on /home/cadey/.uml/tEwIjm/mconsole
Checking host MADV_REMOVE support...OK
workingset: timestamp_bits=62 max_order=14 bucket_order=0
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered (default)
io scheduler bfq registered
loop: module loaded
NET: Registered protocol family 17
Initialized stdio console driver
Using a channel type which is configured out of UML
setup_one_line failed for device 1 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 2 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 3 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 4 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 5 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 6 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 7 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 8 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 9 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 10 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 11 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 12 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 13 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 14 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 15 : Configuration failed
Console initialized on /dev/tty0
console [tty0] enabled
console [mc-1] enabled
Failed to initialize ubd device 0 :Couldn't determine size of device's file
VFS: Mounted root (hostfs filesystem) on device 0:11.
devtmpfs: mounted
This architecture does not have kernel memory protection.
Run /bin/sh as init process
/bin/sh: can't access tty; job control turned off
random: fast init done
/ #

Waxqabadyada kor ku xusan ayaa na siin doona nidaamka martida ugu yaraan, oo aan lahayn waxyaabo ay ka mid yihiin /proc ama magaca martida loo qoondeeyey. Tusaale ahaan, isku day amarrada soo socda:

- uname -av
- cat /proc/self/pid
- hostname

Si aad uga baxdo martida, ku qor exit ama saxafada control-d. Tani waxay dili doontaa qolofka ay ku xigto argagaxa kernel:

/ # exit
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
fish: “./linux root=/dev/root rootflag…” terminated by signal SIGABRT (Abort)

Waxaan helnay argagaxa kernel-ka sababtoo ah kernel-ka Linux wuxuu u maleynayaa in habka bilaabista uu had iyo jeer socdo. La'aanteed, nidaamku ma sii shaqeyn karo oo burburo. Laakiin maadaama tani ay tahay habka isticmaale-habka, wax soo saarka ka soo baxa ayaa isu soo dira SIGABRT, taasoo keenta wax soo saar.

Dejinta shabakada martida

Waana meesha ay arrimuhu ka khaldamaan. Isku xirka Habka Isticmaalaha Linux waa meesha fikradda xaddidan ee "qaabka isticmaalaha" uu bilaabo inuu kala tago. Ka dib oo dhan, sida caadiga ah heerka nidaamka, shabakadu waa xaddidan tahay mudnaanta leh hababka fulinta dhammaanteen sababo la fahmi karo.

Ogow. per .: waxaad wax badan ka akhrisan kartaa fursadaha kala duwan ee la shaqaynta shabakada UML halkan.

Socdaal ku socda Slirp

Si kastaba ha ahaatee, waxaa jira qalab qadiimi ah oo ku dhawaad ​​aan la taageerin oo la yiraahdo Sibiqso, kaas oo Isticmaalaha Mode Linux uu la macaamili karo shabakada. Waxay u shaqeysaa sida heerka isticmaale ee TCP/IP oo kale umana baahna wax ogolaansho nidaam ah si ay u shaqeyso. Qalabkani wuxuu ahaa la sii daayay 1995dii, iyo update u dambeeyay waa taariikhaysan 2006. Slirp aad buu u da' weyn yahay. Inta lagu jiro wakhtiga taageero la'aan iyo updates, compilers ayaa tagay ilaa hadda in qalabkan waxaa lagu tilmaami karaa oo kaliya sida kood qudhuntay.

Markaa aan ka soo dejinno Slirp meelaha Ubuntu oo aan isku dayno inaan socodsiino:

sudo apt-get install slirp
/usr/bin/slirp
Slirp v1.0.17 (BETA)

Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.

IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)

Type five zeroes (0) to exit.

[autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud]

SLiRP Ready ...
fish: “/usr/bin/slirp” terminated by signal SIGSEGV (Address boundary error)

Allaw. Aan rakibno Slirp's debugger oo aragno haddii aan ogaan karno waxa halkan ka socda:

sudo apt-get install gdb slirp-dbgsym
gdb /usr/bin/slirp
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/slirp...Reading symbols from /usr/lib/debug/.build-id/c6/2e75b69581a1ad85f72ac32c0d7af913d4861f.debug...done.
done.
(gdb) run
Starting program: /usr/bin/slirp
Slirp v1.0.17 (BETA)

Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.

IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)

Type five zeroes (0) to exit.

[autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud]

SLiRP Ready ...

Program received signal SIGSEGV, Segmentation fault.
                                                    ip_slowtimo () at ip_input.c:457
457     ip_input.c: No such file or directory.

Qaladka ayaa nagu garaacaya khadkaan. Aan eegno is dulfuulanka, waxaa laga yaabaa inay wax nagu caawiyaan halkaas:

(gdb) bt full
#0  ip_slowtimo () at ip_input.c:457
        fp = 0x55784a40
#1  0x000055555556a57c in main_loop () at ./main.c:980
        so = <optimized out>
        so_next = <optimized out>
        timeout = {tv_sec = 0, tv_usec = 0}
        ret = 0
        nfds = 0
        ttyp = <optimized out>
        ttyp2 = <optimized out>
        best_time = <optimized out>
        tmp_time = <optimized out>
#2  0x000055555555b116 in main (argc=1, argv=0x7fffffffdc58) at ./main.c:95
No locals.

Halkan waxaan ku aragnaa in shilku dhaco inta lagu guda jiro bilawga wareegga ugu weyn marka sibxashadu isku daydo inay hubiso wakhtiyada. Halkaa marka ay marayso, waa in aan ka tanaasulaa isku dayga khaladka. Laakiin aan aragno in Slirp uu ka dhisay noocyo kala duwan oo shaqo ah. Waxaan dib ugala soo degay kaydkii si toos ah goobta Sourceforge, sababtoo ah in wax laga soo jiido halkaas oo loo maro khadka taliska waa xanuun:

cd ~/dl
wget https://xena.greedo.xeserv.us/files/slirp-1.0.16.tar.gz
tar xf slirp-1.0.16.tar.gz
cd slirp-1.0.16/src
./configure --prefix=$HOME/prefix/slirp
make

Halkan waxaan ku aragnaa digniino ku saabsan hawlaha gudaha ee aan la qeexin, taas oo ah, ku saabsan awood la'aanta in la isku xiro faylka binary ee ka dhashay. Waxay u muuqataa in intii u dhaxaysay 2006 iyo bartan, gcc joojisay soo saarista calaamadaha loo isticmaalo hawlaha gudaha ee faylalka la soo ururiyey ee dhexdhexaadka ah. Aan isku dayno inaan bedelno ereyga muhiimka ah inline faallo madhan oo eeg natiijada:

vi slirp.h
:6
a
<enter>
#define inline /**/
<escape>
:wq
make

Maya. Tani sidoo kale ma shaqaynayso. Wali ma heli karo calaamadaha hawlahan.

Halkaa markay marayso, waan quustay oo waxaan bilaabay inaan eego Github Heroku dhis baakadaha. Aragtidaydu waxay ahayd in qaar ka mid ah xirmooyinka dhismaha Heroku ay ka koobnaan doonaan binary-yada aan u baahanahay. Aakhirkii, baadi goobkii ayaa ii horseeday halkan ka daawo. Waan soo degay oo aan ka furay uml.tar.gz oo helay kuwan soo socda:

total 6136
-rwxr-xr-x 1 cadey cadey   79744 Dec 10  2017 ifconfig*
-rwxr-xr-x 1 cadey cadey     373 Dec 13  2017 init*
-rwxr-xr-x 1 cadey cadey  149688 Dec 10  2017 insmod*
-rwxr-xr-x 1 cadey cadey   66600 Dec 10  2017 route*
-rwxr-xr-x 1 cadey cadey  181056 Jun 26  2015 slirp*
-rwxr-xr-x 1 cadey cadey 5786592 Dec 15  2017 uml*
-rwxr-xr-x 1 cadey cadey     211 Dec 13  2017 uml_run*

Kani waa binary-ga sibidhka ah! ma shaqeeyaa?

./slirp
Slirp v1.0.17 (BETA) FULL_BOLT

Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.

IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)

Type five zeroes (0) to exit.

[autodetect SLIP/CSLIP, MTU 1500, MRU 1500]

SLiRP Ready ...

Ma burburto - markaa waa inay shaqeysaa! Aynu ku dhex beerno binary-gan ~/bin/slirp:

cp slirp ~/bin/slirp

Haddii ay dhacdo abuuraha xirmada uu ka saaro, I muraayad sameeyey.

Dejinta shabakadda

Hadda aynu ku xidhno shabkada kernel-ka martidayada. Cusbooneysii fursadaha bilaabista:

linux 
  root=/dev/root 
  rootfstype=hostfs 
  rootflags=$HOME/prefix/uml-demo 
  rw 
  mem=64M 
  eth0=slirp,,$HOME/bin/slirp 
  init=/bin/sh

Hadda aan shidno shabakadda:

mount -t proc proc proc/
mount -t sysfs sys sys/

ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
route add default gw 10.0.2.2

Labada amar ee ugu horreeya qaabeynta /proc и /sys lagama maarmaanka u ah shaqada ifconfig, kaas oo dejinaya interface-ka shabakadda si uu ula xiriiro Slirp. Kooxda route wuxuu dejiyaa miiska marinka kernel si uu ugu qasbo dhammaan taraafikada in loo diro tunnel-ka Slirp. Aan tan ku hubinno weydiinta DNS:

nslookup google.com 8.8.8.8
Server:    8.8.8.8
Address 1: 8.8.8.8 dns.google

Name:      google.com
Address 1: 172.217.12.206 lga25s63-in-f14.1e100.net
Address 2: 2607:f8b0:4006:81b::200e lga25s63-in-x0e.1e100.net

Waxay shaqeysaa!

Xusuusin halkii .: Sida muuqata, boostada asalka ah waxay ku qoran tahay miiska miiska oo leh kaar shabakad fiilo leh, ama qaabayn kale oo aan u baahnayn darawalo dheeraad ah. Laptop-ka leh WiFi 8265 ee Intel, khaladku wuxuu dhacaa marka shabakada kor loo qaado

/ # ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
slirp_tramp failed - errno = 2
ifconfig: ioctl 0x8914 failed: No such file or directory
/ #

Sida muuqata, kernelku lama xidhiidhi karo darawalka kaadhka shabakada. Isku dayga lagu soo ururiyo firmware-ka kernel-ka, nasiib darro, ma hagaajin xaaladda. Waqtiga daabacaadda, suurtagal ma ahayn in xal loo helo qaabeyntan. Qaababka fudud (tusaale ahaan, gudaha Virtualbox), interface-ku si sax ah ayuu u kacayaa.

Aynu si toos ah u jiheyno qoraalka qolofka soo socota:

#!/bin/sh
# init.sh

mount -t proc proc proc/
mount -t sysfs sys sys/
ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
route add default gw 10.0.2.2

echo "networking set up"

exec /tini /bin/sh

Oo calaamadee in la fulin karo:

chmod +x init.sh

Kadibna waxaan ku samayn doonaa isbeddelo khadka taliska kernel:

linux 
  root=/dev/root 
  rootfstype=hostfs 
  rootflags=$HOME/prefix/uml-demo 
  rw 
  mem=64M 
  eth0=slirp,,$HOME/bin/slirp 
  init=/init.sh

Aynu ku celino:

SLiRP Ready ...
networking set up
/bin/sh: can't access tty; job control turned off

nslookup google.com 8.8.8.8
Server:    8.8.8.8
Address 1: 8.8.8.8 dns.google

Name:      google.com
Address 1: 172.217.12.206 lga25s63-in-f14.1e100.net
Address 2: 2607:f8b0:4004:800::200e iad30s09-in-x0e.1e100.net

Shabakadu waa deggan tahay!

docker file

Si aan kuugu fududeeyo inaad waxaas oo dhan hubiso, waan soo ururiyay Dockerfile, Kaas oo otomaatig u noqda inta badan tillaabooyinka lagu sharraxay oo ku siinaya qaabayn shaqaynaysa. Waxaan sidoo kale leeyahay kernel hore loo habeeyey, kaas oo leh wax kasta oo lagu qeexay boostada. Laakiin waxaa muhiim ah in la fahmo in halkan aan ku qeexay kaliya goobta ugu yar.

Waxaan rajeynayaa in qoraalkan uu kaa caawiyay inaad fahamto sida kor loogu qaado kernel martida. Waxay soo baxday inay tahay nooc ka mid ah daanyeerka, laakiin daabacaadda waxaa loo raray inay noqoto hage dhammaystiran oo ku saabsan dhisidda, ku rakibidda iyo habaynta Habka Isticmaalaha Linux ee hoos yimaada noocyada casriga ah ee nidaamyada hawlgalka qoyskan. Talaabooyinka xiga waa in ay ku jiraan ku rakibida adeegyada iyo software-ka kale ee horeyba ugu jiray nidaamka martida. Mar haddii sawirada weelka Docker ay yihiin kuwa daamur ee la dacaayadeeyay, waa inaad awood u yeelatid inaad sawirka ku soo saarto docker export, ka dibna go'aami dariiqa rakibaadda ee xididka nidaamka faylka kernel-ka martida. Hagaag, ka dibna fuli qoraalka qolofka.

Mahad gaar ah waxaa leh Rkene oo ka socda #lobsters oo ku yaal Freenode. Haddaanan gacantiisa ka saarin Slirp, ma aanan gaarteen ilaa hadda. Wax fikrad ah kama haysto sida nidaamkiisa Slackware uu si sax ah ugu shaqeeyo slirp, laakiin nidaamyadayda Ubuntu iyo Alpine ma aqbalin dharbaaxo iyo binary Rkene ayaa ii soo jeediyay. Laakiin waxaa igu filan in ugu yaraan ay wax ii shaqeeyaan.

Source: www.habr.com

Add a comment