API tools faq
paste
Advertisement
AceBlade258

no idmap - success

AceBlade258
Jan 10th, 2023
24
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 32.23 KB | None | 0 0
raw download clone embed print report
  1. [aceblade258@fs01 ~]$ sudo /usr/bin/podman pod create --name dlbox -p 7878:7878 -p 8686:8686 -p 8989:8989 -p 8080:8080 -p 6789:6789 -p 6881:6881 -p 6881:6881/udp -p 9696:9696 --replace --log-level=debug
  2. INFO[0000] /usr/bin/podman filtering at log level debug
  3. DEBU[0000] Called create.PersistentPreRunE(/usr/bin/podman pod create --name dlbox -p 7878:7878 -p 8686:8686 -p 8989:8989 -p 8080:8080 -p 6789:6789 -p 6881:6881 -p 6881:6881/udp -p 9696:9696 --replace --log-level=debug)
  4. DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
  5. DEBU[0000] Using conmon: "/usr/bin/conmon"
  6. DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db
  7. DEBU[0000] Using graph driver
  8. DEBU[0000] Using graph root /var/lib/containers/storage
  9. DEBU[0000] Using run root /run/containers/storage
  10. DEBU[0000] Using static dir /var/lib/containers/storage/libpod
  11. DEBU[0000] Using tmp dir /run/libpod
  12. DEBU[0000] Using volume path /var/lib/containers/storage/volumes
  13. DEBU[0000] Set libpod namespace to ""
  14. DEBU[0000] Cached value indicated that overlay is supported
  15. DEBU[0000] Cached value indicated that overlay is supported
  16. DEBU[0000] Cached value indicated that metacopy is not being used
  17. DEBU[0000] Cached value indicated that native-diff is usable
  18. DEBU[0000] backingFs=xfs, projectQuotaSupported=false, useNativeDiff=true, usingMetacopy=false
  19. INFO[0000] [graphdriver] using prior storage driver: overlay
  20. DEBU[0000] Initializing event backend journald
  21. DEBU[0000] Configured OCI runtime runj initialization failed: no valid executable found for OCI runtime runj: invalid argument
  22. DEBU[0000] Configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
  23. DEBU[0000] Configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
  24. DEBU[0000] Configured OCI runtime krun initialization failed: no valid executable found for OCI runtime krun: invalid argument
  25. DEBU[0000] Using OCI runtime "/usr/bin/crun"
  26. INFO[0000] Setting parallel job count to 25
  27. DEBU[0000] Adding port mapping from 7878 to 7878 length 1 protocol ""
  28. DEBU[0000] Adding port mapping from 8686 to 8686 length 1 protocol ""
  29. DEBU[0000] Adding port mapping from 8989 to 8989 length 1 protocol ""
  30. DEBU[0000] Adding port mapping from 8080 to 8080 length 1 protocol ""
  31. DEBU[0000] Adding port mapping from 6789 to 6789 length 1 protocol ""
  32. DEBU[0000] Adding port mapping from 6881 to 6881 length 1 protocol ""
  33. DEBU[0000] Adding port mapping from 6881 to 6881 length 1 protocol "udp"
  34. DEBU[0000] Adding port mapping from 9696 to 9696 length 1 protocol ""
  35. DEBU[0000] Strongconnecting node 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f
  36. DEBU[0000] Pushed 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f onto stack
  37. DEBU[0000] Finishing node 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f. Popped 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f off stack
  38. DEBU[0000] Removing container 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f
  39. DEBU[0000] Cleaning up container 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f
  40. DEBU[0000] Network is already cleaned up, skipping...
  41. DEBU[0000] Container 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f storage is already unmounted, skipping...
  42. DEBU[0000] Removing all exec sessions for container 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f
  43. DEBU[0000] Container 437c4a2b7b59f3345183301bbc9dcee86ad4ce69cdce5e74d606162b8db35b6f storage is already unmounted, skipping...
  44. DEBU[0000] Removing pod cgroup machine.slice/machine-libpod_pod_1291e9cf027a6588327191e9d2e3844666c05289cf46c5e72fccc78f788344dd.slice
  45. DEBU[0000] Looking up image "localhost/podman-pause:4.3.1-1668180253" in local containers storage
  46. DEBU[0000] Normalized platform linux/amd64 to {amd64 linux [] }
  47. DEBU[0000] Trying "localhost/podman-pause:4.3.1-1668180253" ...
  48. DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/run/containers/storage]@a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63"
  49. DEBU[0000] Found image "localhost/podman-pause:4.3.1-1668180253" as "localhost/podman-pause:4.3.1-1668180253" in local containers storage
  50. DEBU[0000] Found image "localhost/podman-pause:4.3.1-1668180253" as "localhost/podman-pause:4.3.1-1668180253" in local containers storage ([overlay@/var/lib/containers/storage+/run/containers/storage]@a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63)
  51. DEBU[0000] exporting opaque data as blob "sha256:a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63"
  52. DEBU[0000] Created cgroup path machine.slice/machine-libpod_pod_c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772.slice for parent machine.slice and name libpod_pod_c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772
  53. DEBU[0000] Created cgroup machine.slice/machine-libpod_pod_c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772.slice
  54. DEBU[0000] Got pod cgroup as machine.slice/machine-libpod_pod_c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772.slice
  55. DEBU[0000] Looking up image "localhost/podman-pause:4.3.1-1668180253" in local containers storage
  56. DEBU[0000] Normalized platform linux/amd64 to {amd64 linux [] }
  57. DEBU[0000] Trying "localhost/podman-pause:4.3.1-1668180253" ...
  58. DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/run/containers/storage]@a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63"
  59. DEBU[0000] Found image "localhost/podman-pause:4.3.1-1668180253" as "localhost/podman-pause:4.3.1-1668180253" in local containers storage
  60. DEBU[0000] Found image "localhost/podman-pause:4.3.1-1668180253" as "localhost/podman-pause:4.3.1-1668180253" in local containers storage ([overlay@/var/lib/containers/storage+/run/containers/storage]@a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63)
  61. DEBU[0000] exporting opaque data as blob "sha256:a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63"
  62. DEBU[0000] Inspecting image a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63
  63. DEBU[0000] exporting opaque data as blob "sha256:a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63"
  64. DEBU[0000] Inspecting image a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63
  65. DEBU[0000] Inspecting image a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63
  66. DEBU[0000] Inspecting image a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63
  67. DEBU[0000] using systemd mode: false
  68. DEBU[0000] setting container name c5e0316aebb0-infra
  69. DEBU[0000] Loading seccomp profile from "/usr/share/containers/seccomp.json"
  70. DEBU[0000] Successfully loaded 1 networks
  71. DEBU[0000] Allocated lock 1 for container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182
  72. DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/run/containers/storage]@a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63"
  73. DEBU[0000] exporting opaque data as blob "sha256:a2b97da56d29630f4c07cdfadf0251f73143a040c586742ce44e94e055c18c63"
  74. DEBU[0000] Cached value indicated that idmapped mounts for overlay are supported
  75. DEBU[0000] Created container "8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182"
  76. DEBU[0000] Container "8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182" has work directory "/var/lib/containers/storage/overlay-containers/8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182/userdata"
  77. DEBU[0000] Container "8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182" has run directory "/run/containers/storage/overlay-containers/8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182/userdata"
  78. c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772
  79. DEBU[0000] Called create.PersistentPostRunE(/usr/bin/podman pod create --name dlbox -p 7878:7878 -p 8686:8686 -p 8989:8989 -p 8080:8080 -p 6789:6789 -p 6881:6881 -p 6881:6881/udp -p 9696:9696 --replace --log-level=debug)
  80. [aceblade258@fs01 ~]$ sudo podman pod start dlbox --log-level=debugINFO[0000] podman filtering at log level debug
  81. DEBU[0000] Called start.PersistentPreRunE(podman pod start dlbox --log-level=debug)
  82. DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
  83. DEBU[0000] Using conmon: "/usr/bin/conmon"
  84. DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db
  85. DEBU[0000] Using graph driver
  86. DEBU[0000] Using graph root /var/lib/containers/storage
  87. DEBU[0000] Using run root /run/containers/storage
  88. DEBU[0000] Using static dir /var/lib/containers/storage/libpod
  89. DEBU[0000] Using tmp dir /run/libpod
  90. DEBU[0000] Using volume path /var/lib/containers/storage/volumes
  91. DEBU[0000] Set libpod namespace to ""
  92. DEBU[0000] Cached value indicated that overlay is supported
  93. DEBU[0000] Cached value indicated that overlay is supported
  94. DEBU[0000] Cached value indicated that metacopy is not being used
  95. DEBU[0000] Cached value indicated that native-diff is usable
  96. DEBU[0000] backingFs=xfs, projectQuotaSupported=false, useNativeDiff=true, usingMetacopy=false
  97. INFO[0000] [graphdriver] using prior storage driver: overlay
  98. DEBU[0000] Initializing event backend journald
  99. DEBU[0000] Configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
  100. DEBU[0000] Configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
  101. DEBU[0000] Configured OCI runtime krun initialization failed: no valid executable found for OCI runtime krun: invalid argument
  102. DEBU[0000] Configured OCI runtime runj initialization failed: no valid executable found for OCI runtime runj: invalid argument
  103. DEBU[0000] Using OCI runtime "/usr/bin/crun"
  104. INFO[0000] Setting parallel job count to 25
  105. DEBU[0000] Strongconnecting node 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182
  106. DEBU[0000] Pushed 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 onto stack
  107. DEBU[0000] Finishing node 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182. Popped 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 off stack
  108. DEBU[0000] Made network namespace at /run/netns/netns-45ebbe11-c07f-8540-0f3b-b1e8bef1917b for container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182
  109. DEBU[0000] [graphdriver] trying provided driver "overlay"
  110. DEBU[0000] Cached value indicated that overlay is supported
  111. DEBU[0000] Cached value indicated that overlay is supported
  112. DEBU[0000] Cached value indicated that metacopy is not being used
  113. DEBU[0000] backingFs=xfs, projectQuotaSupported=false, useNativeDiff=true, usingMetacopy=false
  114. DEBU[0000] Cached value indicated that idmapped mounts for overlay are supported
  115. DEBU[0000] overlay: mount_data=lowerdir=/var/lib/containers/storage/overlay/l/NETVKZATVPPWRSOW5NHRH7ZJJO:/var/lib/containers/storage/overlay/l/NETVKZATVPPWRSOW5NHRH7ZJJO/../diff1:/var/lib/containers/storage/overlay/l/HSU23LV4IPKPDF3ZH66FCCRB73:/var/lib/containers/storage/overlay/l/HSU23LV4IPKPDF3ZH66FCCRB73/../diff1,upperdir=/var/lib/containers/storage/overlay/fbabbfaef47decce625b7ce92de5f7d1b8a4c805ea6c00785896eee59eac72b4/diff,workdir=/var/lib/containers/storage/overlay/fbabbfaef47decce625b7ce92de5f7d1b8a4c805ea6c00785896eee59eac72b4/work,,context="system_u:object_r:container_file_t:s0:c100,c882"
  116. DEBU[0000] Successfully loaded 1 networks
  117. DEBU[0000] Mounted container "8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182" at "/var/lib/containers/storage/overlay/fbabbfaef47decce625b7ce92de5f7d1b8a4c805ea6c00785896eee59eac72b4/merged"
  118. DEBU[0000] Created root filesystem for container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 at /var/lib/containers/storage/overlay/fbabbfaef47decce625b7ce92de5f7d1b8a4c805ea6c00785896eee59eac72b4/merged
  119. [DEBUG netavark::network::validation] "Validating network namespace..."
  120. [DEBUG netavark::commands::setup] "Setting up..."
  121. [INFO netavark::firewall] Using iptables firewall driver
  122. [DEBUG netavark::network::bridge] Setup network podman
  123. [DEBUG netavark::network::bridge] Container interface name: eth0 with IP addresses [10.88.0.4/16]
  124. [DEBUG netavark::network::bridge] Bridge name: podman0 with IP addresses [10.88.0.1/16]
  125. [DEBUG netavark::network::core_utils] Setting sysctl value for net.ipv4.ip_forward to 1
  126. [DEBUG netavark::network::core_utils] Setting sysctl value for /proc/sys/net/ipv6/conf/eth0/autoconf to 0
  127. [INFO netavark::network::netlink] Adding route (dest: 0.0.0.0/0 ,gw: 10.88.0.1, metric 100)
  128. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-1D8721804F16F created on table nat
  129. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK_FORWARD exists on table filter
  130. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK_FORWARD exists on table filter
  131. [DEBUG netavark::firewall::varktables::helpers] rule -d 10.88.0.0/16 -j ACCEPT exists on table nat and chain NETAVARK-1D8721804F16F
  132. [DEBUG netavark::firewall::varktables::helpers] rule -d 10.88.0.0/16 -j ACCEPT created on table nat and chain NETAVARK-1D8721804F16F
  133. [DEBUG netavark::firewall::varktables::helpers] rule ! -d 224.0.0.0/4 -j MASQUERADE exists on table nat and chain NETAVARK-1D8721804F16F
  134. [DEBUG netavark::firewall::varktables::helpers] rule ! -d 224.0.0.0/4 -j MASQUERADE created on table nat and chain NETAVARK-1D8721804F16F
  135. [DEBUG netavark::firewall::varktables::helpers] rule -s 10.88.0.0/16 -j NETAVARK-1D8721804F16F exists on table nat and chain POSTROUTING
  136. [DEBUG netavark::firewall::varktables::helpers] rule -s 10.88.0.0/16 -j NETAVARK-1D8721804F16F created on table nat and chain POSTROUTING
  137. [DEBUG netavark::firewall::varktables::helpers] rule -d 10.88.0.0/16 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT exists on table filter and chain NETAVARK_FORWARD
  138. [DEBUG netavark::firewall::varktables::helpers] rule -d 10.88.0.0/16 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT created on table filter and chain NETAVARK_FORWARD
  139. [DEBUG netavark::firewall::varktables::helpers] rule -s 10.88.0.0/16 -j ACCEPT exists on table filter and chain NETAVARK_FORWARD
  140. [DEBUG netavark::firewall::varktables::helpers] rule -s 10.88.0.0/16 -j ACCEPT created on table filter and chain NETAVARK_FORWARD
  141. [DEBUG netavark::network::core_utils] Setting sysctl value for net.ipv4.conf.podman0.route_localnet to 1
  142. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-HOSTPORT-SETMARK exists on table nat
  143. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-HOSTPORT-SETMARK exists on table nat
  144. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-HOSTPORT-MASQ exists on table nat
  145. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-HOSTPORT-MASQ exists on table nat
  146. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-DN-1D8721804F16F created on table nat
  147. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-HOSTPORT-DNAT exists on table nat
  148. [DEBUG netavark::firewall::varktables::helpers] chain NETAVARK-HOSTPORT-DNAT exists on table nat
  149. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 6789 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  150. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 6789 created on table nat and chain NETAVARK-DN-1D8721804F16F
  151. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 6789 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  152. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 6789 created on table nat and chain NETAVARK-DN-1D8721804F16F
  153. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:6789 --destination-port 6789 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  154. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:6789 --destination-port 6789 created on table nat and chain NETAVARK-DN-1D8721804F16F
  155. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 6881 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  156. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 6881 created on table nat and chain NETAVARK-DN-1D8721804F16F
  157. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 6881 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  158. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 6881 created on table nat and chain NETAVARK-DN-1D8721804F16F
  159. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:6881 --destination-port 6881 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  160. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:6881 --destination-port 6881 created on table nat and chain NETAVARK-DN-1D8721804F16F
  161. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 7878 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  162. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 7878 created on table nat and chain NETAVARK-DN-1D8721804F16F
  163. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 7878 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  164. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 7878 created on table nat and chain NETAVARK-DN-1D8721804F16F
  165. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:7878 --destination-port 7878 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  166. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:7878 --destination-port 7878 created on table nat and chain NETAVARK-DN-1D8721804F16F
  167. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 8080 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  168. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 8080 created on table nat and chain NETAVARK-DN-1D8721804F16F
  169. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 8080 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  170. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 8080 created on table nat and chain NETAVARK-DN-1D8721804F16F
  171. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:8080 --destination-port 8080 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  172. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:8080 --destination-port 8080 created on table nat and chain NETAVARK-DN-1D8721804F16F
  173. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 8686 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  174. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 8686 created on table nat and chain NETAVARK-DN-1D8721804F16F
  175. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 8686 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  176. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 8686 created on table nat and chain NETAVARK-DN-1D8721804F16F
  177. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:8686 --destination-port 8686 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  178. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:8686 --destination-port 8686 created on table nat and chain NETAVARK-DN-1D8721804F16F
  179. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 8989 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  180. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 8989 created on table nat and chain NETAVARK-DN-1D8721804F16F
  181. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 8989 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  182. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 8989 created on table nat and chain NETAVARK-DN-1D8721804F16F
  183. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:8989 --destination-port 8989 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  184. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:8989 --destination-port 8989 created on table nat and chain NETAVARK-DN-1D8721804F16F
  185. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 9696 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  186. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p tcp --dport 9696 created on table nat and chain NETAVARK-DN-1D8721804F16F
  187. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 9696 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  188. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p tcp --dport 9696 created on table nat and chain NETAVARK-DN-1D8721804F16F
  189. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:9696 --destination-port 9696 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  190. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p tcp --to-destination 10.88.0.4:9696 --destination-port 9696 created on table nat and chain NETAVARK-DN-1D8721804F16F
  191. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p udp --dport 6881 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  192. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 10.88.0.0/16 -p udp --dport 6881 created on table nat and chain NETAVARK-DN-1D8721804F16F
  193. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p udp --dport 6881 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  194. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-HOSTPORT-SETMARK -s 127.0.0.1 -p udp --dport 6881 created on table nat and chain NETAVARK-DN-1D8721804F16F
  195. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p udp --to-destination 10.88.0.4:6881 --destination-port 6881 exists on table nat and chain NETAVARK-DN-1D8721804F16F
  196. [DEBUG netavark::firewall::varktables::helpers] rule -j DNAT -p udp --to-destination 10.88.0.4:6881 --destination-port 6881 created on table nat and chain NETAVARK-DN-1D8721804F16F
  197. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 6789 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  198. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 6789 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  199. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 6881 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  200. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 6881 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  201. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 7878 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  202. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 7878 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  203. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 8080 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  204. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 8080 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  205. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 8686 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  206. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 8686 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  207. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 8989 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  208. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 8989 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  209. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 9696 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  210. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p tcp --dport 9696 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  211. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p udp --dport 6881 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' exists on table nat and chain NETAVARK-HOSTPORT-DNAT
  212. [DEBUG netavark::firewall::varktables::helpers] rule -j NETAVARK-DN-1D8721804F16F -p udp --dport 6881 -m comment --comment 'dnat name: podman id: 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182' created on table nat and chain NETAVARK-HOSTPORT-DNAT
  213. [INFO netavark::commands::setup] dns disabled because aardvark-dns path does not exists
  214. [DEBUG netavark::commands::setup] {
  215. "podman": StatusBlock {
  216. dns_search_domains: Some(
  217. [],
  218. ),
  219. dns_server_ips: Some(
  220. [],
  221. ),
  222. interfaces: Some(
  223. {
  224. "eth0": NetInterface {
  225. mac_address: "2e:16:6d:a3:f4:cf",
  226. subnets: Some(
  227. [
  228. NetAddress {
  229. gateway: Some(
  230. 10.88.0.1,
  231. ),
  232. ipnet: 10.88.0.4/16,
  233. },
  234. ],
  235. ),
  236. },
  237. },
  238. ),
  239. },
  240. }
  241. [DEBUG netavark::commands::setup] "Setup complete"
  242. DEBU[0000] Adding nameserver(s) from network status of '[]'
  243. DEBU[0000] Adding search domain(s) from network status of '[]'
  244. DEBU[0000] found local resolver, using "/run/systemd/resolve/resolv.conf" to get the nameservers
  245. DEBU[0000] /etc/system-fips does not exist on host, not mounting FIPS mode subscription
  246. DEBU[0000] Setting Cgroups for container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 to machine-libpod_pod_c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772.slice:libpod:8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182
  247. DEBU[0000] reading hooks from /usr/share/containers/oci/hooks.d
  248. DEBU[0000] Workdir "/" resolved to host path "/var/lib/containers/storage/overlay/fbabbfaef47decce625b7ce92de5f7d1b8a4c805ea6c00785896eee59eac72b4/merged"
  249. DEBU[0000] Created OCI spec for container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 at /var/lib/containers/storage/overlay-containers/8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182/userdata/config.json
  250. DEBU[0000] /usr/bin/conmon messages will be logged to syslog
  251. DEBU[0000] running conmon: /usr/bin/conmon args="[--api-version 1 -c 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 -u 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 -r /usr/bin/crun -b /var/lib/containers/storage/overlay-containers/8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182/userdata -p /run/containers/storage/overlay-containers/8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182/userdata/pidfile -n c5e0316aebb0-infra --exit-dir /run/libpod/exits --full-attach -s -l journald --log-level debug --syslog --conmon-pidfile /run/containers/storage/overlay-containers/8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182/userdata/conmon.pid --exit-command /usr/bin/podman --exit-command-arg --root --exit-command-arg /var/lib/containers/storage --exit-command-arg --runroot --exit-command-arg /run/containers/storage --exit-command-arg --log-level --exit-command-arg debug --exit-command-arg --cgroup-manager --exit-command-arg systemd --exit-command-arg --tmpdir --exit-command-arg /run/libpod --exit-command-arg --network-config-dir --exit-command-arg --exit-command-arg --network-backend --exit-command-arg netavark --exit-command-arg --volumepath --exit-command-arg /var/lib/containers/storage/volumes --exit-command-arg --runtime --exit-command-arg crun --exit-command-arg --events-backend --exit-command-arg journald --exit-command-arg --syslog --exit-command-arg container --exit-command-arg cleanup --exit-command-arg 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182]"
  252. INFO[0000] Running conmon under slice machine-libpod_pod_c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772.slice and unitName libpod-conmon-8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182.scope
  253. DEBU[0002] Received: 13873
  254. INFO[0002] Got Conmon PID as 13871
  255. DEBU[0002] Created container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 in OCI runtime
  256. DEBU[0002] Starting container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182 with command [/catatonit -P]
  257. DEBU[0002] Started container 8f42e3efce8698a1011028e8f272bfdeb8dc7357bf05a81c193ef8d24d060182
  258. DEBU[0002] Notify sent successfully
  259. c5e0316aebb0df797a681da67e85e1b4b2fd78caa2f83bcfa8e16dec4c250772
  260. DEBU[0002] Called start.PersistentPostRunE(podman pod start dlbox --log-level=debug)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!