Jump to content

[Support] ich777 - Application Dockers

ich777

By ich777
in Docker Containers

Recommended Posts

Recommended

Posted by ich777,

Things have changed a little bit since I'm switched to TurboVNC. Please be sure to create the password first inside the container, to do that open up a terminal from the container (click on the container icon and on 'Console' then type in the following: su $USER vncpasswd ENTER YOUR PASSWORD TWO TIMES AND PRESS ENTER   After that close the terminal and edit the template and create a variable with the Key: 'TURBOVNC_PARAMS' and leave it empty like in this ex

How to set a noVNC password

Recommended by ich777

  • Thanks
  • Like

5 reactions

Go to this post
Recommended

Posted by ich777,

If anything breaks again take a look at this: Click   Or what I would recommend: Stop the container Delete the files "Core.jar" & "JDownloader.jar" and the folders "tmp" & "update" from your jdownloader2 directory Start the container again

Fix: jDownloader2 broken after update

Recommended by ich777

  • Thanks

4 reactions

Go to this post
Recommended

Posted by ich777,

I've tested it now:   On my test server I installed luckyBackup:   Then I clicked console:   There I typed in: cat /luckybackup/.ssh/ssh_host_rsa_key.pub and got this:   There simply mark the whole lines starting from ssh all the way to the last line and click the right mouse button once and click copy from the context menu to copy the contents: Mark only until the end and then close the window.   Then open up a

Set up luckyBackup remote sync

Recommended by ich777

0 reactions

Go to this post
ich777 Grand Master

ich777

Posted
  • Author
Posted
2 hours ago, Merijeek said:

I don't really see any evidence that the script has been loaded/run/whatever in the logs, but it is accessible: 

What does the startup log say? You always have to look at the log files from the container.

 

2 hours ago, Merijeek said:

You can see on the right that it can see the script, and that once I bounced the OVPN container it stayed up with its loopback only. 

But is it executable too?

 

The container is also part from the VPN network correct?

 

Here is what it looks like on my system:

grafik.png.25df415d7330bfdb242010ed0026e1f7.png

 

And this is what indicates that it's started in the container logs:
grafik.thumb.png.4eda341e47674730c0726821c399cae6.png

Link to comment
  • Replies 4.3k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

ich777
ich777

Things have changed a little bit since I'm switched to TurboVNC. Please be sure to create the password first inside the container, to do that open up a terminal from the container (click on the c

ich777
ich777

If anything breaks again take a look at this: Click   Or what I would recommend: Stop the container Delete the files "Core.jar" & "JDownloader.jar" and the folders "tmp" &

ich777
ich777

Summary: Support Thread for ich777 Application Dockers (DirSyncPro, Rapid Photo Downloader,... all available Docker's in the second post) DockerHub: https://hub.docker.com/u/ich777/   P

Posted Images

Merijeek Apprentice

Merijeek

Posted
Posted (edited)

Argh, wrote these stupid things a few times and it felt like info kept changing. 

 

So, from the top one more time. 

 

Script wasn't executable, so I fixed that.

 

Attaching TVH log. Nothing interesting (to me).

 

From the container I can manually run the script: 

 

root@8aa46458dbc4:/etc/cont-init.d# ./91-connected-containers 
fetch http://dl-cdn.alpinelinux.org/alpine/v3.20/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.20/community/x86_64/APKINDEX.tar.gz
v3.20.1-94-g87a0c982bb1 [http://dl-cdn.alpinelinux.org/alpine/v3.20/main]
v3.20.1-96-g8bab5148359 [http://dl-cdn.alpinelinux.org/alpine/v3.20/community]
OK: 24152 distinct packages available
OK: 538 MiB in 311 packages

 

No mention of starting connected containers. 

 

image.thumb.png.8acfbc1df6893eb04090ab4febf0be29.png

 

...and to add to the "I have no idea what is going on here", if I stop the OVPN container, the TVH container stops completely. If I restart the OVPN container, the TVH container stops completely. 

 

Silly question...is this (from one of your containers):

 

image.thumb.png.1fd40809eb8d4c6a70c6056567fa0cc1.png

 

Supposed to be added to the non-ich777 containers AS WELL AS the alpine script?

 

tvh.txt

Edited by Merijeek
Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
7 hours ago, Merijeek said:

Script wasn't executable, so I fixed that.

Nice, maybe that was the whole issue.

 

7 hours ago, Merijeek said:

No mention of starting connected containers. 

Because you are missing that line in your script, but that is nothing to worry about.

 

7 hours ago, Merijeek said:

...and to add to the "I have no idea what is going on here", if I stop the OVPN container, the TVH container stops completely. If I restart the OVPN container, the TVH container stops completely. 

Good news, this means that it is actually working. The culprit to that is that in the extra parameters "--restart=unless-stopped" is missing, the connected containers function completely relies on that.

If you add that to the Extra Prameters (with advanced view enabled in the template) it will work.

 

7 hours ago, Merijeek said:

Supposed to be added to the non-ich777 containers AS WELL AS the alpine script?

Nope because everything is defined in the script, please change the script to that for the alpine based containers and it should work more reliably: 

#!/bin/sh
apk update
apk add netcat-openbsd
echo "---Starting connected containers watchdog on 127.0.0.1:27286---"
(nc 127.0.0.1 27286 && { echo "---Connection to connected container lost, restarting in 15 seconds...---"; sleep 15; kill -SIGTERM 1; } || echo "---Couldn't connect to connected containers---") &

(the changes add the missing line and also increase the restart time to 15 seconds <- this was done to be sure that the VPN container is started and connected)

 

I think the issue was that the script wasn't executable.

Link to comment
Xodarap Noob

Xodarap

Posted
Posted
On 6/5/2022 at 9:10 AM, lhw1221 said:

Thunderbird dose not work anymore after i restartet my server resently 
LOGS:

---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Checking configuration for noVNC---
Nothing to do, noVNC resizing set to default
Nothing to do, noVNC qaulity set to default
Nothing to do, noVNC compression set to default
---Taking ownership of data...---
---Starting...---
---Version Check---

---Thunderbird v91.10.0 up-to-date---
---Preparing Server---
---Resolution check---
---Checking for old logfiles---
---Checking for old display lock files---
---Starting TurboVNC server---
---Starting Fluxbox---
Fluxbox crashed with exit code 1. Respawning..
Fluxbox crashed with exit code 1. Respawning..
---Starting noVNC server---
WebSocket server settings:
- Listen on :8080
- Web server. Web root: /usr/share/novnc
- No SSL/TLS support (no cert file)
- Backgrounding (daemon)
Fluxbox crashed with exit code 1. Respawning..
Fluxbox crashed with exit code 1. Respawning..
---Starting Thunderbird---
Unable to init server: Could not connect: Connection refused
Error: cannot open display: :99

after this it loops showing the same everytime

Hello,
I have the exact same error. 

I got it working once and after a restart I get this.

My container and docker is running on a synology diskstation. 
I already reinstalled docker, deleted the docker folder, reinstalled the container in docker and restartet the diskstation. 
The error still occures.

Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
4 minutes ago, Xodarap said:

I got it working once and after a restart I get this.

So it is working once after installing the container, do you mean you restart your Synology Disk station or do you just restart the container?

 

5 minutes ago, Xodarap said:

The error still occures.

Can you please tell me what Docker version what is used on your Synology box?

What environment variables do you use or even better what docker run command do you use?

Link to comment
Xodarap Noob

Xodarap

Posted
Posted
2 minutes ago, ich777 said:

So it is working once after installing the container, do you mean you restart your Synology Disk station or do you just restart the container?

I did both several times.

 

 

2 minutes ago, ich777 said:

Can you please tell me what Docker version what is used on your Synology box?

Docker version is 20.10.3-1308, which seems to be the newest version.

2 minutes ago, ich777 said:

What environment variables do you use or even better what docker run command do you use?

here my env variables:

image.thumb.png.b37e1c127f36a0b958c3502b97d5bf02.png

image.thumb.png.29a5569dfb99bb3c9034fb8320ade08d.png

 

Run command is /opt/scripts/start.sh

Link to comment
Xodarap Noob

Xodarap

Posted
Posted
10 minutes ago, ich777 said:

So it is working once after installing the container, do you mean you restart your Synology Disk station or do you just restart the container?

 

Can you please tell me what Docker version what is used on your Synology box?

What environment variables do you use or even better what docker run command do you use?

datestreamcontent

2024-07-11T08:37:03.593445996ZstdoutFluxbox crashed with exit code 1.  Respawning..

2024-07-11T08:37:03.591565911ZstdoutError: cannot open display: :99

2024-07-11T08:37:03.539995914Zstdout---Starting Thunderbird---

2024-07-11T08:37:02.422123975ZstdoutFluxbox crashed with exit code 1.  Respawning..

2024-07-11T08:37:01.535297222Zstdout  - Backgrounding (daemon)

2024-07-11T08:37:01.535097945Zstdout  - No SSL/TLS support (no cert file)

2024-07-11T08:37:01.534552629Zstdout  - Web server. Web root: /usr/share/novnc

2024-07-11T08:37:01.534298962Zstdout  - Listen on :8080

2024-07-11T08:37:01.534108445ZstdoutWebSocket server settings:

2024-07-11T08:37:01.112697365ZstdoutFluxbox crashed with exit code 1.  Respawning..

2024-07-11T08:37:00.128997086Zstdout---Starting noVNC server---

2024-07-11T08:36:59.773466622ZstdoutFluxbox crashed with exit code 1.  Respawning..

2024-07-11T08:36:58.568328885ZstdoutFluxbox crashed with exit code 1.  Respawning..

2024-07-11T08:36:58.128573769Zstdout---Starting Fluxbox---

2024-07-11T08:36:55.955941940Zstdout---Starting TurboVNC server---

2024-07-11T08:36:55.927831316Zstdout---Checking for old display lock files---

2024-07-11T08:36:55.909576290Zstdout---Checking for old logfiles---

2024-07-11T08:36:55.909513171Zstdout---Resolution check---

2024-07-11T08:36:55.909285530Zstdout---Preparing Server---

2024-07-11T08:36:55.908297594Zstdout---Thunderbird not found!---

2024-07-11T08:36:54.313463063Zstdout---Starting...---

2024-07-11T08:36:54.297677146Zstdout---Taking ownership of data...---

2024-07-11T08:36:54.297198602ZstdoutNothing to do, noVNC compression set to default

2024-07-11T08:36:54.293068621ZstdoutNothing to do, noVNC qaulity set to default

2024-07-11T08:36:54.288029253ZstdoutNothing to do, noVNC resizing set to default

2024-07-11T08:36:54.253179266Zstdout---Checking configuration for noVNC---

2024-07-11T08:36:54.252797376Zstdout---No optional script found, continuing---

2024-07-11T08:36:54.225810256Zstdout---Checking for optional scripts---

2024-07-11T08:36:54.225651804Zstdout---Setting umask to 000---

2024-07-11T08:36:53.752119258Zstdout---Ensuring GID: 100 matches user---

2024-07-11T08:36:53.442870409Zstdout---Ensuring UID: 99 matches user---

Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
5 minutes ago, Xodarap said:

here my env variables:

And you are sure that the UID 99 and GID 100 exist on your Synology?

I assume that's why it's crashing because my container tries to fix the permission on container startup and Thunderbird is also started as this user.

Make sure that the UID and GID matches a user that is actually able to write from and to the directories and of course exists on your Synology.

 

6 minutes ago, Xodarap said:

Docker version is 20.10.3-1308, which seems to be the newest version.

The latest version is 27.0.3, see here.

The version you are running is from 2022, see here.

 

I really can't say if it's related to the Docker version (the user that had the issue back then was also running a outdated Unraid version IIRC).

Link to comment
AlexON Apprentice

AlexON

Posted
Posted (edited)

What a surprise...

I had left the container abandoned, in its unmodified version. I just installed the container as you posted it and put it aside. A few days later, I decided to take a look at it again and there, I see that the download was done automatically during the night.. (around 1:30-2 am). But naturally, this surprise was short-lived because I am not able despite the modification of the IP in my system to retrieve the updates via UNRAID. Can you share with me how you configured your /etc/apt/service.list (Your Debian in your case...)so that I can repair my error (I don't see where it could be by the way). Thank you.

  

alexandre@alexandre-All-Series:/etc/apt$ sudo apt update
Ign :1 http://192.168.1.87:980/ubuntu/dists jammy InRelease
Ign :2 http://192.168.1.87:980/ubuntu/dists jammy-security InRelease
Ign :3 http://192.168.1.87:980/ubuntu/dists jammy-updates InRelease
Ign :4 http://192.168.1.87:980/ubuntu/dists jammy-backports InRelease
Err :5 http://192.168.1.87:980/ubuntu/dists jammy Release
404 Not Found [IP : 192.168.1.87 980]
Err:6 http://192.168.1.87:980/ubuntu/dists jammy-security Release
404 Not Found [IP: 192.168.1.87 980]
Err:7 http://192.168.1.87:980/ubuntu/dists jammy-updates Release
404 Not Found [IP: 192.168.1.87 980]
Err:8 http://192.168.1.87:980/ubuntu/dists jammy-backports Release
404 Not Found [IP: 192.168.1.87 980]
Reading package lists... Done
E: The repository http://192.168.1.87:980/ubuntu/dists jammy Release has no Release file.
N: Updates from such a repository cannot be performed securely, and are disabled by default.
N: See the apt-secure(8) man pages for repository creation and user configuration details.
E: The http://192.168.1.87:980/ubuntu/dists jammy-security Release repository does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are disabled by default.
N: See the apt-secure(8) man pages for repository creation and user configuration details.
E: The http://192.168.1.87:980/ubuntu/dists jammy-updates Release repository does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are disabled by default.
N: See the apt-secure(8) man pages for repository creation and user configuration details.
E: The repository http://192.168.1.87:980/ubuntu/dists jammy-backports Release has no Release file.
N: Updates from such a repository cannot be performed securely, and are disabled by default.
N: See the apt-secure(8) man pages for repository creation and user configuration details.

 

 

Capture d’écran du 2024-07-11 16-12-14.png

 

Capture d’écran du 2024-07-11 16-28-26.png

Edited by AlexON
Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
25 minutes ago, AlexON said:

Can you share with me how you configured your /etc/apt/service.list (Your Debian in your case...)so that I can repair my error (I don't see where it could be by the way).

Sure, just as described here:

grafik.thumb.png.e4da65fa07a7e55b93f6ef1b2c74955f.png

 

In your case just remove "/dists", apt finds this path automatically, that's simply how apt works.

 

For Debian (which is almost the same) it looks like that:

grafik.png.e5db849c4badc4b72f153b192c059bd1.png

 

...and after running "apt udpate" you will get something like that:

grafik.png.d99a2b497ff2c40a77544de4147a500a.png

Link to comment
AlexON Apprentice

AlexON

Posted
Posted (edited)
2 hours ago, ich777 said:

Sure, just as described here:

grafik.thumb.png.e4da65fa07a7e55b93f6ef1b2c74955f.png

 

In your case just remove "/dists", apt finds this path automatically, that's simply how apt works.

 

For Debian (which is almost the same) it looks like that:

grafik.png.e5db849c4badc4b72f153b192c059bd1.png

 

...and after running "apt udpate" you will get something like that:

grafik.png.d99a2b497ff2c40a77544de4147a500a.png

Quote 
alexandre@alexandre-All-Series:/etc/apt$ sudo apt update
Réception de :1 http://192.168.1.87:980/ubuntu jammy InRelease [270 kB]
Réception de :2 http://192.168.1.87:980/ubuntu jammy-updates InRelease [128 kB]
Réception de :3 http://192.168.1.87:980/ubuntu jammy-security InRelease [129 kB]
Réception de :4 http://192.168.1.87:980/ubuntu jammy-backports InRelease [127 kB]
Ign :5 http://192.168.1.87:980/ubuntu jammy/main i386 Packages       
Réception de :6 http://192.168.1.87:980/ubuntu jammy/main amd64 Packages [1 395 kB]
Réception de :7 http://192.168.1.87:980/ubuntu jammy/main Translation-fr [486 kB]
Réception de :8 http://192.168.1.87:980/ubuntu jammy/main Translation-en [510 kB]
Réception de :9 http://192.168.1.87:980/ubuntu jammy/main amd64 DEP-11 Metadata [423 kB]
Réception de :10 http://192.168.1.87:980/ubuntu jammy/main DEP-11 48x48 Icons [100,0 kB]                
Réception de :11 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64 Icons [148 kB]                
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]          
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]          
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Atteint :19 http://archive.ubuntu.com/ubuntu jammy InRelease
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Réception de :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons [15,8 kB]
Ign :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons
Réception de :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages [30,4 kB]
Réception de :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages [30,4 kB]
Réception de :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages [30,4 kB]
Réception de :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages [30,4 kB]
Ign :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages
Réception de :45 http://192.168.1.87:980/ubuntu jammy/universe i386 Packages [7 474 kB]
Ign :45 http://192.168.1.87:980/ubuntu jammy/universe i386 Packages
Réception de :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons [69,3 kB]
Réception de :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons [69,3 kB]
Réception de :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons [69,3 kB]
Réception de :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons [69,3 kB]
Ign :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons
Réception de :52 http://192.168.1.87:980/ubuntu jammy/multiverse i386 Packages [112 kB]
Réception de :52 http://192.168.1.87:980/ubuntu jammy/multiverse i386 Packages [112 kB]
Ign :52 http://192.168.1.87:980/ubuntu jammy/multiverse i386 Packages
Réception de :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons [214 B]
Réception de :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons [214 B]
Réception de :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons [214 B]
Réception de :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons [214 B]
Réception de :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons [214 B]
Ign :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons
Réception de :5 http://192.168.1.87:980/ubuntu jammy/main i386 Packages [1 040 kB]
Ign :5 http://192.168.1.87:980/ubuntu jammy/main i386 Packages      
Réception de :62 http://192.168.1.87:980/ubuntu jammy-updates/main i386 Packages [655 kB]
Ign :62 http://192.168.1.87:980/ubuntu jammy-updates/main i386 Packages
Réception de :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons [29 B]
Réception de :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons [29 B]
Réception de :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons [29 B]
Réception de :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons [29 B]
Réception de :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons [29 B]
Réception de :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons [29 B]
Ign :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons
Réception de :71 http://192.168.1.87:980/ubuntu jammy-updates/restricted i386 Packages [38,9 kB]
Ign :71 http://192.168.1.87:980/ubuntu jammy-updates/restricted i386 Packages
Réception de :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons [29 B]
Réception de :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons [29 B]
Réception de :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons [29 B]
Réception de :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons [29 B]
Ign :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons
Réception de :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages [716 kB]
Réception de :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages [716 kB]
Réception de :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages [716 kB]
Réception de :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages [716 kB]
Ign :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages
Réception de :83 http://192.168.1.87:980/ubuntu jammy-updates/universe DEP-11 64x64@2 Icons [29 B]
Réception de :83 http://192.168.1.87:980/ubuntu jammy-updates/universe DEP-11 64x64@2 Icons [29 B]
Réception de :83 http://192.168.1.87:980/ubuntu jammy-updates/universe DEP-11 64x64@2 Icons [29 B]
Ign :83 http://192.168.1.87:980/ubuntu jammy-updates/universe DEP-11 64x64@2 Icons
Réception de :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages [4 744 B]
Réception de :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages [4 744 B]
Réception de :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages [4 744 B]
Réception de :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages [4 744 B]
Ign :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages
Réception de :92 http://192.168.1.87:980/ubuntu jammy-updates/multiverse DEP-11 64x64@2 Icons [29 B]
Réception de :92 http://192.168.1.87:980/ubuntu jammy-updates/multiverse DEP-11 64x64@2 Icons [29 B]
Ign :92 http://192.168.1.87:980/ubuntu jammy-updates/multiverse DEP-11 64x64@2 Icons
Réception de :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages [497 kB]
Réception de :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages [497 kB]
Réception de :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages [497 kB]
Réception de :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages [497 kB]
Ign :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages
Réception de :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons [29 B]
Réception de :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons [29 B]
Réception de :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons [29 B]
Réception de :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons [29 B]
Ign :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons
Réception de :105 http://192.168.1.87:980/ubuntu jammy-security/restricted i386 Packages [37,3 kB]
Réception de :105 http://192.168.1.87:980/ubuntu jammy-security/restricted i386 Packages [37,3 kB]
Ign :105 http://192.168.1.87:980/ubuntu jammy-security/restricted i386 Packages
Réception de :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons [29 B]
Réception de :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons [29 B]
Réception de :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons [29 B]
Réception de :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons [29 B]
Ign :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons
Réception de :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages [617 kB]
Réception de :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages [617 kB]
Réception de :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages [617 kB]
Réception de :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages [617 kB]
Ign :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages
Réception de :118 http://192.168.1.87:980/ubuntu jammy-security/universe DEP-11 64x64@2 Icons [29 B]
Ign :118 http://192.168.1.87:980/ubuntu jammy-security/universe DEP-11 64x64@2 Icons
Ign :120 http://192.168.1.87:980/ubuntu jammy-security/multiverse i386 Packages
Ign :121 http://192.168.1.87:980/ubuntu jammy-security/multiverse DEP-11 64x64@2 Icons
Ign :122 http://192.168.1.87:980/ubuntu jammy-backports/main i386 Packages
Ign :123 http://192.168.1.87:980/ubuntu jammy-backports/main DEP-11 64x64@2 Icons
Ign :124 http://192.168.1.87:980/ubuntu jammy-backports/restricted DEP-11 64x64@2 Icons
Ign :125 http://192.168.1.87:980/ubuntu jammy-backports/universe i386 Packages
Ign :126 http://192.168.1.87:980/ubuntu jammy-backports/universe DEP-11 64x64@2 Icons
Ign :127 http://192.168.1.87:980/ubuntu jammy-backports/multiverse DEP-11 64x64@2 Icons
Ign :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons
Ign :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages
Ign :45 http://192.168.1.87:980/ubuntu jammy/universe i386 Packages
Ign :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons
Ign :52 http://192.168.1.87:980/ubuntu jammy/multiverse i386 Packages
Ign :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons
Ign :5 http://192.168.1.87:980/ubuntu jammy/main i386 Packages   
Ign :62 http://192.168.1.87:980/ubuntu jammy-updates/main i386 Packages
Ign :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons
Ign :71 http://192.168.1.87:980/ubuntu jammy-updates/restricted i386 Packages
Ign :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons
Ign :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages
Ign :83 http://192.168.1.87:980/ubuntu jammy-updates/universe DEP-11 64x64@2 Icons
Ign :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages
Ign :92 http://192.168.1.87:980/ubuntu jammy-updates/multiverse DEP-11 64x64@2 Icons
Ign :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages
Ign :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons
Ign :105 http://192.168.1.87:980/ubuntu jammy-security/restricted i386 Packages
Ign :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons
Ign :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages
Ign :118 http://192.168.1.87:980/ubuntu jammy-security/universe DEP-11 64x64@2 Icons
Ign :120 http://192.168.1.87:980/ubuntu jammy-security/multiverse i386 Packages
Ign :121 http://192.168.1.87:980/ubuntu jammy-security/multiverse DEP-11 64x64@2 Icons
Ign :122 http://192.168.1.87:980/ubuntu jammy-backports/main i386 Packages
Ign :123 http://192.168.1.87:980/ubuntu jammy-backports/main DEP-11 64x64@2 Icons
Ign :124 http://192.168.1.87:980/ubuntu jammy-backports/restricted DEP-11 64x64@2 Icons
Ign :125 http://192.168.1.87:980/ubuntu jammy-backports/universe i386 Packages
Ign :126 http://192.168.1.87:980/ubuntu jammy-backports/universe DEP-11 64x64@2 Icons
Ign :127 http://192.168.1.87:980/ubuntu jammy-backports/multiverse DEP-11 64x64@2 Icons
Ign :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons
Ign :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages
Ign :45 http://192.168.1.87:980/ubuntu jammy/universe i386 Packages
Ign :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons
Ign :52 http://192.168.1.87:980/ubuntu jammy/multiverse i386 Packages
Ign :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons
Ign :5 http://192.168.1.87:980/ubuntu jammy/main i386 Packages   
Ign :62 http://192.168.1.87:980/ubuntu jammy-updates/main i386 Packages
Ign :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons
Ign :71 http://192.168.1.87:980/ubuntu jammy-updates/restricted i386 Packages
Ign :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons
Ign :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages
Ign :83 http://192.168.1.87:980/ubuntu jammy-updates/universe DEP-11 64x64@2 Icons
Ign :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages
Ign :92 http://192.168.1.87:980/ubuntu jammy-updates/multiverse DEP-11 64x64@2 Icons
Ign :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages
Ign :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons
Ign :105 http://192.168.1.87:980/ubuntu jammy-security/restricted i386 Packages
Ign :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons
Ign :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages
Ign :118 http://192.168.1.87:980/ubuntu jammy-security/universe DEP-11 64x64@2 Icons
Ign :120 http://192.168.1.87:980/ubuntu jammy-security/multiverse i386 Packages
Ign :121 http://192.168.1.87:980/ubuntu jammy-security/multiverse DEP-11 64x64@2 Icons
Ign :122 http://192.168.1.87:980/ubuntu jammy-backports/main i386 Packages
Ign :123 http://192.168.1.87:980/ubuntu jammy-backports/main DEP-11 64x64@2 Icons
Ign :124 http://192.168.1.87:980/ubuntu jammy-backports/restricted DEP-11 64x64@2 Icons
Ign :125 http://192.168.1.87:980/ubuntu jammy-backports/universe i386 Packages
Ign :126 http://192.168.1.87:980/ubuntu jammy-backports/universe DEP-11 64x64@2 Icons
Ign :127 http://192.168.1.87:980/ubuntu jammy-backports/multiverse DEP-11 64x64@2 Icons
Err :12 http://192.168.1.87:980/ubuntu jammy/main DEP-11 64x64@2 Icons
  404  Not Found [IP : 192.168.1.87 980]
Ign :40 http://192.168.1.87:980/ubuntu jammy/restricted i386 Packages
Ign :45 http://192.168.1.87:980/ubuntu jammy/universe i386 Packages
Ign :47 http://192.168.1.87:980/ubuntu jammy/universe DEP-11 64x64@2 Icons
Ign :52 http://192.168.1.87:980/ubuntu jammy/multiverse i386 Packages
Ign :55 http://192.168.1.87:980/ubuntu jammy/multiverse DEP-11 64x64@2 Icons
Ign :5 http://192.168.1.87:980/ubuntu jammy/main i386 Packages
Ign :62 http://192.168.1.87:980/ubuntu jammy-updates/main i386 Packages
Err :64 http://192.168.1.87:980/ubuntu jammy-updates/main DEP-11 64x64@2 Icons
  404  Not Found [IP : 192.168.1.87 980]
Ign :71 http://192.168.1.87:980/ubuntu jammy-updates/restricted i386 Packages
Ign :73 http://192.168.1.87:980/ubuntu jammy-updates/restricted DEP-11 64x64@2 Icons
Ign :78 http://192.168.1.87:980/ubuntu jammy-updates/universe i386 Packages
Ign :83 http://192.168.1.87:980/ubuntu jammy-updates/universe DEP-11 64x64@2 Icons
Ign :87 http://192.168.1.87:980/ubuntu jammy-updates/multiverse i386 Packages
Ign :92 http://192.168.1.87:980/ubuntu jammy-updates/multiverse DEP-11 64x64@2 Icons
Ign :95 http://192.168.1.87:980/ubuntu jammy-security/main i386 Packages
Err :100 http://192.168.1.87:980/ubuntu jammy-security/main DEP-11 64x64@2 Icons
  404  Not Found [IP : 192.168.1.87 980]
Ign :105 http://192.168.1.87:980/ubuntu jammy-security/restricted i386 Packages
Ign :108 http://192.168.1.87:980/ubuntu jammy-security/restricted DEP-11 64x64@2 Icons
Ign :113 http://192.168.1.87:980/ubuntu jammy-security/universe i386 Packages
Ign :118 http://192.168.1.87:980/ubuntu jammy-security/universe DEP-11 64x64@2 Icons
Ign :120 http://192.168.1.87:980/ubuntu jammy-security/multiverse i386 Packages
Ign :121 http://192.168.1.87:980/ubuntu jammy-security/multiverse DEP-11 64x64@2 Icons
Ign :122 http://192.168.1.87:980/ubuntu jammy-backports/main i386 Packages
Err :123 http://192.168.1.87:980/ubuntu jammy-backports/main DEP-11 64x64@2 Icons
  404  Not Found [IP : 192.168.1.87 980]
Ign :124 http://192.168.1.87:980/ubuntu jammy-backports/restricted DEP-11 64x64@2 Icons
Ign :125 http://192.168.1.87:980/ubuntu jammy-backports/universe i386 Packages
Ign :126 http://192.168.1.87:980/ubuntu jammy-backports/universe DEP-11 64x64@2 Icons
Ign :127 http://192.168.1.87:980/ubuntu jammy-backports/multiverse DEP-11 64x64@2 Icons
Ign :122 http://192.168.1.87:980/ubuntu jammy-backports/main i386 Packages
654 kb received in 2s (332 kb/s)
Reading package lists... Done
E: Unable to retrieve http://192.168.1.87:980/ubuntu/dists/jammy/main/dep11/[email protected] 404 Not Found [IP: 192.168.1.87 980]
E: Unable to retrieve http://192.168.1.87:980/ubuntu/dists/jammy-updates/main/dep11/[email protected] 404 Not Found [IP: 192.168.1.87 980]
E: Unable to retrieve http://192.168.1.87:980/ubuntu/dists/jammy-security/main/dep11/[email protected] 404 Not Found [IP: 192.168.1.87 980]
E: Unable to recover http://192.168.1.87:980/ubuntu/dists/jammy-backports/main/dep11/[email protected] 404 Not Found [IP: 192.168.1.87 980]
E: Some index files failed to download, were skipped, or old ones were used instead.

 

Finally, things are finally moving forward but from what I can understand, he hasn't downloaded all the packages. Do you know how I can recover them? Because at the moment, I cannot do an apt-upgrade if necessary...

 

Edited by AlexON
Link to comment
Xodarap Noob

Xodarap

Posted
Posted
19 hours ago, ich777 said:

And you are sure that the UID 99 and GID 100 exist on your Synology?

I assume that's why it's crashing because my container tries to fix the permission on container startup and Thunderbird is also started as this user.

Make sure that the UID and GID matches a user that is actually able to write from and to the directories and of course exists on your Synology.

I just checked this. When I use my standard user it says uid=1026 and GID=100. 
I am not sure which user i should check the ids. Or do i define the user with entering the uid? In this case maybe the UID99 was wrong.

But somehow today everything is working again. 
Just by using securitytypes=none instead of vnc.

 

19 hours ago, ich777 said:

The latest version is 27.0.3, see here.

The version you are running is from 2022, see here.

 

I really can't say if it's related to the Docker version (the user that had the issue back then was also running a outdated Unraid version IIRC).

 

Ah okay. But the version I'm using seems to be the newest version integrated into Diskstation natively. 
And as it is working again today this seems to be not an issue.

  • Like 1
Link to comment
AlexON Apprentice

AlexON

Posted
Posted (edited)
18 hours ago, AlexON said:

Finally, things are finally moving forward but from what I can understand, he hasn't downloaded all the packages. Do you know how I can recover them? Because at the moment, I cannot do an apt-upgrade if necessary...

 

I think I understand that is a bug in apt-mirror witch dates back several years. The problem here and the solution here is that there is a script to issue via docker (probably) to correct this problem. If anything, what can we confirm?

 

https://github.com/apt-mirror/apt-mirror/issues/102

 

Sorry I adding a new links...

https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/2044556

 

and the fix https://github.com/Stifler6996/apt-mirror

 

EDIT : @ich777Yep.. If you continue the github conversation, someone offers their own apt-mirror docker with the fix integrated. I don't know if you would be interested in doing the same on yours just in case. This also affects Debian apparently. Afterwards, no wonder, it's the same source code.

Edited by AlexON
Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
26 minutes ago, AlexON said:

I think I understand that is a bug in apt-mirror witch dates back several years. The problem here and the solution here is that there is a script to issue via docker (probably) to correct this problem. If anything, what can we confirm?

What problem, I really don't understand. What is missing?

My mirror is working perfectly fine, I even can install Debian from scratch with my mirror.

 

Please note that I use the Debian apt-mirror package which has to patches applied IIRC (yes, even for the Ubuntu container).

Link to comment
AlexON Apprentice

AlexON

Posted
Posted (edited)

I declare that there is a bug not fixed for several years which affects the apt-mirror command when you want to create a mirror. Latest posts on github are from 2023 and also at https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/2044556. Afterwards, when I use a Debian LXC to do tests, I don't encounter any problems. But if you are using Debian/Ubuntu as your main system, you will definitely encounter this problem. I can always try via a Debian VM or whatever, but again, Debian/Ubuntu, it's the same thing chosen. In any case, I fixed (at least I think) the problem with the github that I gave you if you want to see and integrate it. I'm just waiting for docker to update (because I can't do it manually) and see if that permanently fixes the problem or not. To be continued

 

EDIT: I'm looking through a Debian VM (I have your 2 dockers) to see if I encounter the same problem. Logically yes, but in any case, I come back to you because I myself want to understand what is happening.

Edited by AlexON
Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
55 minutes ago, AlexON said:

I declare that there is a bug not fixed for several years which affects the apt-mirror command when you want to create a mirror.

Can you please declare the bug more in detail?

 

When I create the mirror it immediately starts to download what I configured at full blast.

What I do is:

  1. Deploy the container
  2. Configure mirror.list how I need it
  3. Restart the container

 

After step three it starts to download the things that I've configured.

 

55 minutes ago, AlexON said:

I'm looking through a Debian VM (I have your 2 dockers) to see if I encounter the same problem. Logically yes, but in any case, I come back to you because I myself want to understand what is happening.

You always talk about a "problem" what is the exact problem?

 

55 minutes ago, AlexON said:

Afterwards, when I use a Debian LXC to do tests

What kind of tests? Do you install the mirror there or do you try to download packages?

 

You haven't even posted anything how you configured the container itself? What network do you use for your container, is host access on?

 

55 minutes ago, AlexON said:

But if you are using Debian/Ubuntu as your main system

I use Debian Bookworm as my main system and also on my Notebook and I can pull updates as usual.

 

The apt-mirror that I use is from Debian itself not from GitHub and they apply these patches:

https://sources.debian.org/patches/apt-mirror/0.5.4-2/

 

I use my Debian Mirror on a daily basis and it is working fine for me, it downloads the packages on the schedule that I created in the container template.

Link to comment
AlexON Apprentice

AlexON

Posted
Posted (edited)
28 minutes ago, ich777 said:

Can you please declare the bug more in detail?

 

When I create the mirror it immediately starts to download what I configured at full blast.

What I do is:

  1. Deploy the container
  2. Configure mirror.list how I need it
  3. Restart the container

 

After step three it starts to download the things that I've configured.

 

You always talk about a "problem" what is the exact problem?

 

What kind of tests? Do you install the mirror there or do you try to download packages?

 

You haven't even posted anything how you configured the container itself? What network do you use for your container, is host access on?

 

I use Debian Bookworm as my main system and also on my Notebook and I can pull updates as usual.

 

The apt-mirror that I use is from Debian itself not from GitHub and they apply these patches:

https://sources.debian.org/patches/apt-mirror/0.5.4-2/

 

I use my Debian Mirror on a daily basis and it is working fine for me, it downloads the packages on the schedule that I created in the container template.

ahhh now I understand... Debian fixed the bug under apt-mirror and not Canonical Ubuntu. The version changed from 0.5.4-1 to 0.5.4.2. This explains why you don't see what I'm trying to explain.

 

This also confirms that there is an unfixed bug in your docker without you knowing it. And which is not your fault but the Ubuntu editor. You have the fix now, if you are interested in fixing this bug.

 

look by yourself.

image.png.ef362a7ea50609a5f5ad4a9ab9a981f5.pngimage.png.33974fce592371dd2d532ffbd7654b52.png

 

Edited by AlexON
Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
14 minutes ago, AlexON said:

ahhh now I understand... Debian fixed the bug under apt-mirror and not Ubuntu. The version changed from 0.5.4-1 to 0.5.4.2. This explains why you don't see what I'm trying to explain.

I really don't understand... Here you say that the bug is fixed...

 

14 minutes ago, AlexON said:

This also confirms that there is an unfixed bug in your docker without you knowing it. And which is not your fault but the Ubuntu editor. You have the fix now, if you are interested in fixing this bug.

And here you say that the bug isn't fixed...

 

What?

 

 

In case you think I use the package from Ubuntu for the Ubuntu-APT-Mirror you are wrong.

As I explained above, I use both for Ubuntu-APT-Mirror and Debian-APT-Mirror both the same package from Debian.

 

In other words both containers use:
http://deb.debian.org/debian bookworm/main amd64 apt-mirror all 0.5.4-2 [18.8 kB]

Link to comment
AlexON Apprentice

AlexON

Posted
Posted (edited)

Ok, I understand that English is not my mother tongue but despite the sources I give you, you still don't understand. I seriously don't know what to do anymore by leading me to believe that you don't consult any sources... I don't see anything else. Seriously, I understand that you use apt-mirror from Debian to create your containers but for the version 22.02 of Ubuntu that you made, the bug is persistent and not corrected. I documented them and gave you the solution to fix it. Concerning myself, I think I managed to patch the problem on your docker but I must confirm it when it does its update at the time you gave it, i.e. 10 p.m. (home time) but as long as I don't I haven't checked, I'm not sure of anything.

Edited by AlexON
Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted
Just now, AlexON said:

Ok, I understand that English is not my mother tongue but despite the sources I give you, you still don't understand. I seriously don't know what to do anymore.

Have you read my post here:

 

I even tried the Ubuntu-APT-Mirror in that post and it is working fine, please look at the screenshots.

Link to comment
ich777 Grand Master

ich777

Posted
  • Author
Posted

@AlexON btw, the bug that you are talking about is it related to this one here.

I even posted a workaround in the linked GitHub issue.

 

EDIT: I now deprecated the Ubuntu-APT-Mirror since I have no use for as I did this container on request and it is really hard to test for me.

It is of course still functional if you want to use it and you can of course fork and customize it to your likings.

Maybe you can bring it back to Unraid in a working state. :)

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing
×
×
  • Create New...