Get the old Docker images and containers back into operation

Docker Desktop
18

I didn’t bother with this when I installed Linux on VMware. My goal is to see my .war running in Linux. I didn’t bother with anything else as my ultimate goal is to create the dynamic website with Docker on a real server. Which path do you recommend me to take? Which approach do you use? I accept advice very gladly.

gi@Ubuntu-22:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:0e:13:9e brd ff:ff:ff:ff:ff:ff
    altname enp2s1
    inet 192.168.17.130/24 brd 192.168.17.255 scope global dynamic noprefixroute ens33
       valid_lft 1678sec preferred_lft 1678sec
    inet6 fe80::c84e:b5e9:4166:73da/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:1d:22:25:3e brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:1dff:fe22:253e/64 scope link 
       valid_lft forever preferred_lft forever
5: veth57fa555@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether fa:9d:ab:60:c2:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::f89d:abff:fe60:c289/64 scope link 
       valid_lft forever preferred_lft forever
gi@Ubuntu-22:~$

Immagine
Immagine750×734 23.2 KB 

ipconfig

Configurazione IP di Windows


Scheda Ethernet Ethernet:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:

Scheda Ethernet VirtualBox Host-Only Network #2:

   Suffisso DNS specifico per connessione:
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::714d:4ea3:b04d:ce71%15
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.99.1
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Gateway predefinito . . . . . . . . . :

Scheda Ethernet VirtualBox Host-Only Network:

   Suffisso DNS specifico per connessione:
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::85f9:4396:c0a:a525%13
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.56.1
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Gateway predefinito . . . . . . . . . :

Scheda LAN wireless Connessione alla rete locale (LAN)* 1:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:

Scheda LAN wireless Connessione alla rete locale (LAN)* 14:

   Stato supporto. . . . . . . . . . . . : Supporto disconnesso
   Suffisso DNS specifico per connessione:

Scheda Ethernet VMware Network Adapter VMnet1:

   Suffisso DNS specifico per connessione:
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::8112:1851:88f2:3ac4%12
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.13.1
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Gateway predefinito . . . . . . . . . :

Scheda Ethernet VMware Network Adapter VMnet8:

   Suffisso DNS specifico per connessione:
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::4464:9fbf:2ab8:bbe8%2
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.17.1
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Gateway predefinito . . . . . . . . . :

Scheda LAN wireless Wi-Fi:

   Suffisso DNS specifico per connessione:
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::9d3a:2c19:558c:9b66%25
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.43.55
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Gateway predefinito . . . . . . . . . : 192.168.43.1