Replies: 14 comments 1 reply
-
Same here, seems like the issue is inside the 4d0fd514210a image. |
Beta Was this translation helpful? Give feedback.
-
I think youre using docker inside an unpriviliged container on proxmox. EDIT: |
Beta Was this translation helpful? Give feedback.
-
|
Okay, in my digging research:
It's very late now, i have to sleep, maybe someone else can look through for unusual gid/uid or whatever else. |
Beta Was this translation helpful? Give feedback.
-
|
okay further digging, the text files and the gid/uid's seems okay. tbh, it makes no sense to me why speedtest-traker doesn't work, while every other docker image im using works flawless. That are the running containers, that have no issues whatsoever. im gonna check as next if there is an adduser example folder either. However, the workaround for this situation would be atm, to make either an zfs dataset and format it as ext4, then run the LXC Container with docker on that storage. However, if i know more, ill post. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, after further digging: onlyoffice: has all the files??: inspecting onlyoffice image with tar: comparing with speedtest-tracker: I don't see a single difference.... the only other possibility here is, that simply the error from docker is maybe completely wrong, maybe it fails before or after and just outputs the last file it was doing, or some before, who knows. Maybe someone else has more Luck in finding the issue/solution to it. Cheers |
Beta Was this translation helpful? Give feedback.
-
|
You are spending all these efforts but both are failing to provide BASIC INFO: are you using docker in a LXC container or VM? Are you using ZFS? Docker is not officially supported in Proxmox LXC containers with ZFS, but they work in latest versions only, with latest kernels and only if privileged LXCs. So don't waste time checking docker images, they are perfectly fine, it's your environment. |
Beta Was this translation helpful? Give feedback.
-
|
This is my Debian 12 LXC container for Docker on Proxmox 8.x and ZFS, you need to properly configure it (check red rectangle):
|
Beta Was this translation helpful? Give feedback.
-
|
Bro, i have multiple Proxmox Servers, almost all with ZFS Exclusive Storage, one of them has an EXT4 Storage tho.
My second post in this "Discussion" mentions already Proxmox in an Unpriviliged Container. However, i was trying to find out why every other Docker image works with an unpriviliged container on zfs, while speedtest-tracker don't. However, it's obviously not only a fault of the Unpriviliged Container or "My Environment", since that would mean, that no other Docker image would work either. |
Beta Was this translation helpful? Give feedback.
-
Yo, Bro...wazzuuup...:) Jokes apart: I have many dockers on Proxmox, the critical ones are in VMs, because Proxmox DOES NOT SUPPORT Docker in LXC containers. Just read Proxmox official documentation. If you have an issue with Docker in LXC, there's no way to have OFFICIAL SUPPORT. Read their forums, there are a lot of issues open with docker in LXC, and the answer is always the same. The only way I've managed to make docker work reliably in LXC is in privileged containers. But that is not supported either, so I'm on my own in case of problems. And no, it is not like running docker on Proxmox itself, it's a separate environment luckily. It's true that from a security standpoint it's not recommended, but it was the only way to have separation and make all the apps I needed working fine. Acceptable compromise for me.
No they're not identical. ST uses other images, it's based on s6, it's a laravel framework app (PHP). OnlyOffice is a .NET app IIRC, but you can't say two apps are IDENTICAL. Analyze them first.
No, that is a totally wrong assumption. You don't use ALL apps/services that are out there. For example, I was having issues with Piwigo...all my apps were working, but Piwigo wasn't working, it threw weird errors when starting it up with docker compose. After a lot of tries, I set it up in my main docker that is in a VM, and had ZERO issues. So, bottom line is: you are trying to make something work that is NOT SUPPORTED in the Proxmox environment, if it works fine, but if it doesn't, don't try to blame Proxmox, the app, the image or whatever, ok? That is why it's not supported, because it's not 100% compatible. I'm pretty sure in the future they'll make it work fine so I can finally use an unprivileged LXC, but I'll have to wait... |
Beta Was this translation helpful? Give feedback.
-
|
Okay bro 😂 I never blamed anyone, either Proxmox or the Dev of Speedtest-tracker in any of the posts. As you seen, im not even asked anybody to help and tryed to figure out myself, what the issue could be. The whole discussion long, i tryed to figure out what's different, by myself, until i wasn't successful, since onlyoffice throw all my assumptions away 😂 So it's actually not clear to me, what you're trying to say other as it doesn't work on Unprivileged container and we don't have any support. To be clear, if i wanted any support, or would assume that this is a bug of Speedtest-tracker, i would have opened a GitHub issue... The Proxmox documentation is a bit slow, since they still recommend vfio modules that doesn't exist anymore on kernel 6.2, just to mention one if the documentation issues. That feature completeness will happen with zfs 2.2, probably in 1-3 Months. So as you see, im not blaming anyone 😂 Cheers |
Beta Was this translation helpful? Give feedback.
-
|
No problem bro, just wanted to clear some things out. Love your enthusiasm, but what I'm telling you is that until Docker in LXC + ZFS will be officially supported by Proxmox, don't waste too much time and energy trying to make it work. Trust me, I've been there, done that. :) I remember when ZFS could be used in LXC with Docker only through FUSE...then all of the sudden, with recent versions of edge kernels 6.x (before 8.x was out), overlay2 with ZFS started working fine also without FUSE (only in privileged LXCs). There's my post on their forum regarding LXC+ZFS+Docker overlay2, and devs couldn't tell me HOW it was working. I thought it had to be the new kernel versions or something, but they said they didn't know exactly what made it work. Obviously, privileged LXC. There are many things going on with all these integrations man...we can't control everything and try to understand why something doesn't work and others do...sometimes even devs don't have a clue. :D But that's the fun part of having a homelab...tinkering...:) Cheers mate. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I've been there either everywhere 😂 But somehow i got it always working on my part 😂 However, hopefully that pain will be all and for once over with openzfs 2.2 😂 Cheers |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help guys! It's really appreciated. I wish there was a better answer, but I guess at this point, I just need to wait or rebuild my Docker instance. Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
There is a workaround to get it working, but it's määh... Simply create a temporary dataset, it could be that you need to uninstall apparmor in your lxc container, im doing it anyway always... I think that after that you can even pull/update newer speedtest-tracker images, because the directorys somehow already exist. however, that solution is just shit, thats why i tryed to find a more "proper" way xD Cheers |
Beta Was this translation helpful? Give feedback.
-
|
It's a few months later and this is still an issue. I too normally use LXC containers and try my best to avoid using docker at all if possible. I figured I'd give docker a shot on this go around and I got the same issue as OP. I have plenty of other unprivileged containers using docker but as @alexdelprete had mentioned there is no direct support. It looks like you are either running this in your Docker VM if you are using Proxmox or doing the manual install. |
Beta Was this translation helpful? Give feedback.
-
Hey everyone,
I'm trying to install this on a Proxmox server running a Docker container. My run command is the following:
docker run -d --name speedtest-tracker --restart unless-stopped
-p 8080:80
-p 8443:443
-e PUID=1000
-e PGID=1000
-v /docker/speedtest-tracker/data:/config
-v /docker/speedtest-tracker/web:/etc/ssl/web
ghcr.io/alexjustesen/speedtest-tracker:latest
When I run this, I get an error and have had no lucking finding this exact error on my many searches.
docker: failed to register layer: unlinkat /usr/share/doc/adduser/examples/adduser.local.conf.examples: invalid argument.
If anyone has any suggestions to resolve this, I would be very grateful! I'm fairly new to docker and am still learning. This one has me stumped.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions