| # | Post Title | Result Info | Date | User | Forum |
| eBlock 4.0.2 ThinClient - Android Apps Issues | Relevance | 3 Monaten ago | Joe | eBlocker Open Source Forum |
| | @bpr Since my HP EliteDesk 800 is not an option for me due to the problem with the Intel LAN connection for the eBlocker4, I switched to a new (used) thin client (Lenovo ThinkCentre M75n with Ryzen 3 Pro 3300U, 8GB and 128 GB SSD). First, I used eBlocker3 on this hardware for three weeks to have a basis for comparison. With eBlocker 4.0.2, I observed the following issues. Threema: does not connect initially (red line). Only after briefly disabling HTTPS activation for the smartphone does the connection work and remain active with HTTPS activation until t ... |
| There is now an eBlocker 4 Docker image available for testing! (v. 4.0.2) | Relevance | 3 Monaten ago | Shedowe | eBlocker Open Source Forum |
| | There is now an eBlocker 4 Docker image available for testing! (arm64 & x86_64 worked) Docker Hub: Highlights:- Full eBlocker system (including systemd) inside a container- Runs in a macvlan network as its own device (own IP & MAC)- Persistent root filesystem via volume (`/eblocker-root`) A sample docker-compose setup is included in the Repository Overview on Docker Hub. Docker Run equivalent Using docker run with macvlan requires two steps: first creating the network, then running the container. 1. Create the Macvlan network: (Adjust paren ... |
| eBlocker Docker Container | Relevance | 5 Monaten ago | Lerain | eBlocker Open Source Forum |
| | Greetings, I’m looking for a way to run eBlocker inside a Docker container. I know there’s a VM Edition available for both VirtualBox and VMware, but that’s full virtualization - not Dockerization. I even tried converting the VM image into a Docker container using an OVA-to-Docker converter, but I hit a roadblock due to missing dependencies (qemu-utils and parted). I also tried using the pre-made unclejay/eblocker image, which I thought would be exactly what I needed, but the console logs showed Maven failing to fetch the correct dependencies, so that at ... |
