-
|
I followed the guide, used the docker template. The jail startup errors on this step: Every other package installs fine. Networking works, I can shell into the jail but every time I try apt it reports unmet dependencies for docker-ce of iptables. Running apt --fix-broken install doesn't fix it. I get the same error with that same package. Please let me know what I'm doing wrong. I didn't change the template. I'm on TrueNas Scale Cobia. |
Beta Was this translation helpful? Give feedback.
Answered by
LunkSnee
Aug 6, 2024
Replies: 3 comments 11 replies
-
|
Please collect all information per #135. You stated you're using all defaults, yet it works for other people - so please share as much as you can about your process, the fail points on their own are rarely enough to identify the reason something is failing. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Lockszmith-GH, thanks for the question. I created a network br1 which works great. cd /mnt/mypool/jailmaker
curl --location --remote-name https://raw.githubusercontent.com/Jip-Hop/jailmaker/main/jlmkr.py
chmod +x jlmkr.py
echo "alias jlmkr=\"sudo -E '/mnt/mypool/jailmaker/jlmkr.py'\"" >> ~/.zshrc
source ~/.zshrc
curl --location --remote-name https://raw.githubusercontent.com/Jip-Hop/jailmaker/main/templates/docker/config
jlmkr create --start --config ./config dockerAnd the result is the error I provided. Every other package installs but iptables. click to expand: |
Beta Was this translation helpful? Give feedback.
10 replies
-
|
What about a vanilla debian template, and just attempt to install And also, try different debian generations. |
Beta Was this translation helpful? Give feedback.
-
|
I just tried not using the template, tried debian11 with and without the template, and tried ubuntu-noble with no template. All error on that same file, regardless of the different package names. From ubuntu install |
Beta Was this translation helpful? Give feedback.
-
|
This is very bizzare indeed. I'm thinking data corruption can happen by: network connection, cpu, drive. I have no idea what sort of bug will fail you exactly on the same package regardless of source, but something doesn't like the stream of bytes that you're pulling in. If you still want to pursue this, I can think of the following troubleshooting step: Possible Missing LibraryI've searched a bit the missing file it's complaining about, and it seems that file is part of libc6 - it's a dependent, and should have been installed, but maybe it's worth it to try and reinstall Manual DownloadTry to download the file manually (from here) - either with curl (which I think would give you the same result), but I would also suggest you download it on your PC, and transfer it manually to the jail's rootfs. Also, compare SHA keys to those posted by debian. |
Beta Was this translation helpful? Give feedback.
-
|
I just don't think it can be data corruption. Here's the steps I took and get the same result regardless. This is nuts. /usr/lib/x86_64-linux-gnu/xtables/l/libip6t_hl.so exists on my host TrueNAS system. It is only to enable ipv6 functionality. I wonder if there is something related to ipv6. But I'm not doing anything special that I know of with ipv6. ipv6 works on my TrueNAS. root@test:~# wget http://ftp.br.debian.org/debian/pool/main/i/iptables/iptables_1.8.9-2_amd64.deb
--2024-08-05 18:46:00-- http://ftp.br.debian.org/debian/pool/main/i/iptables/iptables_1.8.9-2_amd64.deb
Resolving ftp.br.debian.org (ftp.br.debian.org)... 200.236.31.3, 2801:82:80ff:8000::4
Connecting to ftp.br.debian.org (ftp.br.debian.org)|200.236.31.3|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 360192 (352K) [application/vnd.debian.binary-package]
Saving to: ‘iptables_1.8.9-2_amd64.deb’
iptables_1.8.9-2_amd64.deb 100%[=====================================================================================================================>] 351.75K 337KB/s in 1.0s
2024-08-05 18:46:02 (337 KB/s) - ‘iptables_1.8.9-2_amd64.deb’ saved [360192/360192]
root@test:~# sha256sum iptables_1.8.9-2_amd64.deb
2928d3ca6ca8a3dc3f423f6752822b1f3614a5ba609ff7806bcba4449ffe90e1 iptables_1.8.9-2_amd64.deb
root@test:~# apt-cache show iptables | grep SHA
SHA256: 2928d3ca6ca8a3dc3f423f6752822b1f3614a5ba609ff7806bcba4449ffe90e1
root@test:~# dpkg -i iptables_1.8.9-2_amd64.deb
(Reading database ... 12295 files and directories currently installed.)
Preparing to unpack iptables_1.8.9-2_amd64.deb ...
Unpacking iptables (1.8.9-2) ...
dpkg: error processing archive iptables_1.8.9-2_amd64.deb (--install):
unable to open '/usr/lib/x86_64-linux-gnu/xtables/libip6t_hl.so.dpkg-new': No such file or directory
Errors were encountered while processing:
iptables_1.8.9-2_amd64.deb |
Beta Was this translation helpful? Give feedback.
-
|
I would agree, this isn't a corruption - it's a missing dependency issue. I wonder if there is a verbose output, anyway - that's what needs to be researched. I'm at my wits end here. I wonder if this link is a similar issue, maybe their solution can be applied here. Anyway, it has to do with the package definition, but somehow it effects you specifically. |
Beta Was this translation helpful? Give feedback.
-
|
As am I. I appreciate your efforts on this... Here's what I did to finally get it working. Mind you, it is ugly and not good practice. Again, thanks for your time and efforts. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
wow, good work! I'm curious if installing a previous version of iptables and then upgrading might work. Anyway, amazing work. Don't know if I helped or steered you in the wrong direction for a while, but I know the satisfaction of solving something so stubborn. Enjoy your docker jail! |
Beta Was this translation helpful? Give feedback.
Answer selected by
LunkSnee
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As am I. I appreciate your efforts on this... Here's what I did to finally get it working. Mind you, it is ugly and not good practice.
In this process of troubleshooting, I was able to verify it wasn't just the one file in the xtables directory, it was multiple files. So to solve it, I excluded the xtables directory from the dpkg install and then copied those files over from an extract of the iptables .deb.
Adding the following custom section to the excerpt of your template file (see "# custom code for iptables fix") works around this weird issue where dpkg.new files aren't being created in the xtables directory. I'm sure this could be cleaned up, but with this I'm able to finish the crea…