Local Repository Copies?
Hi Folks, Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos. I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality. Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure... Any thoughts? Regards, Lew
On 04.05.2024 22:14, Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure...
Any thoughts?
SUSE RMT?
On 5/4/24 12:20, Andrei Borzenkov wrote:
On 04.05.2024 22:14, Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure...
Any thoughts?
SUSE RMT?
I noticed that, but it seemed to be rather complicated and overkill for what I need. I have a few use cases. 1. Local up-to-date copies of the relevant external repos that I can access via NFS from a couple dozen local hosts. NFS access is really FAST for this! 2. The local repos can be virus checked, for what that's worth. 3. I use the local repositories as the source for a process that I run using rsync to create a file containing the deltas to "sneaker net" into an internal subnet without outside network connections. In other words, I have one set of repos that are up-to-date. I have a second set of repos that represent the state of the non-networked repos. rsync can be used to compare the two hierarchies and create a file containing the deltas that can then be moved to and update the repos on the inside. After the process completes, the outside and inside repos are identical. The hosts on the isolated network can then "zypper up" using NFS and be happily updated. I do this once per week or so. The deltas usually fit comfortably on a 32-GB SDcard. Using Red Hat's reposync program I don't have to download hundreds of GB of repo every week, and it's trivially easy to set up. I hope this is all clear, it took me a while to figure out how to do it. Thanks for the pointers! Regards, Lew
On 05.05.2024 04:31, Lew Wolfgang wrote:
Using Red Hat's reposync program I don't have to download hundreds of GB of repo every week, and it's trivially easy to set up.
Well, then use it. What is the problem? SUSE is using the same overall repository format. bor@uefi:~> reposync The program 'reposync' can be found in the following package: * yum-utils [ path: /usr/bin/reposync, repository: openSUSE-20191030-0 ] Try installing with: sudo zypper install yum-utils bor@uefi:~>
On 5/4/24 22:37, Andrei Borzenkov wrote:
On 05.05.2024 04:31, Lew Wolfgang wrote:
Using Red Hat's reposync program I don't have to download hundreds of GB of repo every week, and it's trivially easy to set up.
Well, then use it. What is the problem? SUSE is using the same overall repository format.
bor@uefi:~> reposync
The program 'reposync' can be found in the following package: * yum-utils [ path: /usr/bin/reposync, repository: openSUSE-20191030-0 ]
Try installing with: sudo zypper install yum-utils
Yes, it's just odd that SUSE and friends don't natively support what I'd consider to be core functionality. Indeed, I struggled with this for years before discovering the reposync option. I was using rsync to those openSUSE mirrors that supported it, but I had to do it off-site because my customer doesn't allow external rsync connections on port 873. It was a PITA. I really searched for options too, my mistake was I didn't search Red Hat documentation. It was actually a young assistant I hired who was familiar with Red Hat, who asked me, "Why don't you do it this way?" I was hoping that I just missed something and that openSUSE does natively support this functionality. Since it apparently doesn't, perhaps this dialog will help other users who need to maintain local rpm repositories. Regards, Lew
On 05.05.2024 10:10, Lew Wolfgang wrote:
I was hoping that I just missed something and that openSUSE does natively support this functionality.
I have no idea what the "native support" is supposed to mean. reposync is part of upstream RPM repository. SUSE supports (and is using by default) the same repository format as RH. reposync is available for openSUSE. How exactly reposync is less "native" than rpm itself? You can just as well start complaining that SUSE is using package format originated in RH instead of developing "native solution".
On 2024-05-05 13:58, Andrei Borzenkov wrote:
On 05.05.2024 10:10, Lew Wolfgang wrote:
I was hoping that I just missed something and that openSUSE does natively support this functionality.
I have no idea what the "native support" is supposed to mean. reposync is part of upstream RPM repository. SUSE supports (and is using by default) the same repository format as RH. reposync is available for openSUSE. How exactly reposync is less "native" than rpm itself? You can just as well start complaining that SUSE is using package format originated in RH instead of developing "native solution".
Is there a howto or wiki page explaining how to use it with openSUSE? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 05.05.2024 15:28, Carlos E. R. wrote:
On 2024-05-05 13:58, Andrei Borzenkov wrote:
On 05.05.2024 10:10, Lew Wolfgang wrote:
I was hoping that I just missed something and that openSUSE does natively support this functionality.
I have no idea what the "native support" is supposed to mean. reposync is part of upstream RPM repository. SUSE supports (and is using by default) the same repository format as RH. reposync is available for openSUSE. How exactly reposync is less "native" than rpm itself? You can just as well start complaining that SUSE is using package format originated in RH instead of developing "native solution".
Is there a howto or wiki page explaining how to use it with openSUSE?
bor@tw:~> sudo ln -s ../../zypp/repos.d/repo-update.repo /etc/dnf/repos.d/ bor@tw:~> yum repolist Repository repo-update is listed more than once in the configuration repo id repo name repo-update openSUSE-Tumbleweed-Update bor@tw:~> yum --repo=repo-update reposync -p test-repo Repository repo-update is listed more than once in the configuration openSUSE-Tumbleweed-Update 18 kB/s | 3.3 kB 00:00 allow_vendor_change is disabled. This option is currently not supported for downgrade and distro-sync commands (1/41): update-test-32bit-pkg-5.1-2.2.i586.rpm 20 kB/s | 8.3 kB 00:00 ... (41/41): update-test-trivial-5.2-2.1.x86_64.rpm 18 kB/s | 9.5 kB 00:00 bor@tw:~> Yes, yum does not use /etc/zypp. I suppose, you just link /etc/dnf/repos.d -> /etc/zypp/repos.d No, I do not know why it complains about multiple definitions. May be it actually has some zypp plugins under the hood.
On 2024-05-04 21:14, Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure...
Any thoughts?
https://wiki.jessen.ch/index/How_to_cache_openSUSE_repositories_with_Squid ? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 5/4/24 13:13, Carlos E. R. wrote:
On 2024-05-04 21:14, Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure...
Any thoughts?
https://wiki.jessen.ch/index/How_to_cache_openSUSE_repositories_with_Squid
Interesting. But it seems to be rather complicated, and requires a "custom" daemon. OTOH, the yum reposync program is simple to set up and run. The yum/dnf pieces are all available in the openSUSE repos too. It's a neat idea though. Regards, Lew
On Sunday, 5 May 2024 04:44:09 ACST Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure...
Any thoughts?
Regards, Lew
Do you need to maintain full copies of the repos locally, or would proxying/ caching requests to the repos for installs/updates be good enough? I've used apt-cacher-ng at home and in our corporate network for providing updates for machines that don't have outbound internet access. It caches files locally the first time they're requested and then serves them from the cache for subsequent requests. It works for zypper and yum as well as apt, but the mechanism is slightly different. For zypper and yum it's necessary to modify the repo URL to point to the apt-cacher-ng service on port 3142 (there are 2 documented ways do to that), whereas with apt it's a one-liner in a config file. The port can be changed if needed (e.g. to 8080 or any other arbitrary port). Apt-cacher-ng is available for openSUSE (including TW) but it's necessary to add the server:proxy repo to get it. Regards, Rodney. -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
On 5/5/24 01:05, Rodney Baker wrote:
On Sunday, 5 May 2024 04:44:09 ACST Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure... Do you need to maintain full copies of the repos locally, or would proxying/ caching requests to the repos for installs/updates be good enough?
I've used apt-cacher-ng at home and in our corporate network for providing updates for machines that don't have outbound internet access. It caches files locally the first time they're requested and then serves them from the cache for subsequent requests.
It works for zypper and yum as well as apt, but the mechanism is slightly different. For zypper and yum it's necessary to modify the repo URL to point to the apt-cacher-ng service on port 3142 (there are 2 documented ways do to that), whereas with apt it's a one-liner in a config file. The port can be changed if needed (e.g. to 8080 or any other arbitrary port).
Apt-cacher-ng is available for openSUSE (including TW) but it's necessary to add the server:proxy repo to get it.
Thanks for the suggestion Rodney. But in my case it really makes sense to have a completely local copy of repositories. My off-network machines are completely off-network, the only way to import data is to carry physical media down the hallway and plug it in after checking for malware. Having a local copy also allows easy creation of deltas using rsync. The size of the repos this morning is 1.3-TB, and since corporate policy demands that the media to import data be used only once, it would become expensive to sacrifice a disk drive every week. But the changes from week to week will fit onto a 32-GB SDcard, which can reasonably be used once and thrown away. I've got hundreds of them in my desk drawer. A local copy also allows malware scanning. Clamav works fine, and while it might not be the best choice for detection it's enough to check the box. I updated my local repo last night and ran clamscan on it, the results are included below. Clamav unpacks rpm's, so it really is a valid exercise. This was run on an oldish desktop, I'm sure it would be faster on a modern box. The repo selection is the standard enabled suite for Leap 15.5, including Packman and Nvidia, except the openh264 repo which seems to be having a mirror problem right now. Here's the Clamav report: Known viruses: 8692269 Engine version: 0.103.11 Scanned directories: 165 Scanned files: 326923 Infected files: 0 Data scanned: 726747.85 MB Data read: 1336155.75 MB (ratio 0.54:1) Time: 28876.391 sec (481 m 16 s) Start Date: 2024:05:04 20:40:55 End Date: 2024:05:05 04:42:12 Regards, Lew
On 2024-05-05 19:19, Lew Wolfgang wrote:
On 5/5/24 01:05, Rodney Baker wrote:
On Sunday, 5 May 2024 04:44:09 ACST Lew Wolfgang wrote:
Hi Folks,
...
Apt-cacher-ng is available for openSUSE (including TW) but it's necessary to add the server:proxy repo to get it.
Thanks for the suggestion Rodney. But in my case it really makes sense to have a completely local copy of repositories. My off-network machines are completely off-network, the only way to import data is to carry physical media down the hallway and plug it in after checking for malware.
Having a local copy also allows easy creation of deltas using rsync. The size of the repos this morning is 1.3-TB, and since corporate policy demands that the media to import data be used only once, it would become expensive to sacrifice a disk drive every week. But the changes from week to week will fit onto a 32-GB SDcard, which can reasonably be used once and thrown away. I've got hundreds of them in my desk drawer.
Would they accept CD or DVD? Burn once media. Pointy haired boss comes to my mind. Ok, I go back to my cave, I said nothing :-) -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 5/6/24 00:53, Carlos E. R. wrote:
On 2024-05-05 19:19, Lew Wolfgang wrote:
On 5/5/24 01:05, Rodney Baker wrote:
On Sunday, 5 May 2024 04:44:09 ACST Lew Wolfgang wrote:
Hi Folks,
...
Apt-cacher-ng is available for openSUSE (including TW) but it's necessary to add the server:proxy repo to get it.
Thanks for the suggestion Rodney. But in my case it really makes sense to have a completely local copy of repositories. My off-network machines are completely off-network, the only way to import data is to carry physical media down the hallway and plug it in after checking for malware.
Having a local copy also allows easy creation of deltas using rsync. The size of the repos this morning is 1.3-TB, and since corporate policy demands that the media to import data be used only once, it would become expensive to sacrifice a disk drive every week. But the changes from week to week will fit onto a 32-GB SDcard, which can reasonably be used once and thrown away. I've got hundreds of them in my desk drawer.
Would they accept CD or DVD? Burn once media.
Pointy haired boss comes to my mind. Ok, I go back to my cave, I said nothing :-)
🙂 You don't know the half of it, Carlos! Yes, optical media would work, but even DVD doesn't always have enough capacity. I'd have to use "split" with multiple DVD's. I tried BlueRay disks, but they were a bit funky and unreliable. The 32-GB SDcards work well and don't cost all that much. They're faster too! The PHB doesn't mind paying for them. I've used old spinners to move in the initial repositories. I've got probably dozens of old 1-TB disks that can be sacrificed. The initial load after a new Leap release will easily fit. A Sneaker-Net can have really high bandwidth! Regards, Lew
On 2024-05-06 16:28, Lew Wolfgang wrote:
On 5/6/24 00:53, Carlos E. R. wrote:
On 2024-05-05 19:19, Lew Wolfgang wrote:
On 5/5/24 01:05, Rodney Baker wrote:
On Sunday, 5 May 2024 04:44:09 ACST Lew Wolfgang wrote:
Hi Folks,
...
...
Would they accept CD or DVD? Burn once media.
Pointy haired boss comes to my mind. Ok, I go back to my cave, I said nothing :-)
🙂 You don't know the half of it, Carlos!
I worked at a place, back on 2000, that prohibited WiFi and used Tempest proof glass ;-) Of course, our machines could not be reached from outside. But we could reach outside, and we had an internal SuSE mirror (and redhat and or debian). That was Lucent, born of the split of AT&T.
Yes, optical media would work, but even DVD doesn't always have enough capacity. I'd have to use "split" with multiple DVD's. I tried BlueRay disks, but they were a bit funky and unreliable. The 32-GB SDcards work well and don't cost all that much. They're faster too! The PHB doesn't mind paying for them.
I've used old spinners to move in the initial repositories. I've got probably dozens of old 1-TB disks that can be sacrificed. The initial load after a new Leap release will easily fit.
A Sneaker-Net can have really high bandwidth!
Oh, absolutely! Nothing beats a train load of hard disks ;-) Even a single truck load beats fibre. What throws me out is the requisite of throwing away the media after one use. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 5/6/24 08:33, Carlos E. R. wrote:
A Sneaker-Net can have really high bandwidth!
Oh, absolutely! Nothing beats a train load of hard disks 😉
Even a single truck load beats fibre.
What throws me out is the requisite of throwing away the media after one use.
They want to remove any possibility of data leaving the private network. One can conceive of malware where, if present on the private network, could try to find ways to reach the outside. Disk drives could be contaminated just by mounting on a system. It happens in the Windows World all the time! Regards, Lew
On 2024-05-06 18:02, Lew Wolfgang wrote:
On 5/6/24 08:33, Carlos E. R. wrote:
A Sneaker-Net can have really high bandwidth!
Oh, absolutely! Nothing beats a train load of hard disks 😉
Even a single truck load beats fibre.
What throws me out is the requisite of throwing away the media after one use.
They want to remove any possibility of data leaving the private network. One can conceive of malware where, if present on the private network, could try to find ways to reach the outside. Disk drives could be contaminated just by mounting on a system. It happens in the Windows World all the time!
Just overwrite the media with random data on a non networked machine used solely for erasing media. Could run from a RO-DVD. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 5/6/24 11:12, Carlos E. R. wrote:
On 2024-05-06 18:02, Lew Wolfgang wrote:
On 5/6/24 08:33, Carlos E. R. wrote:
A Sneaker-Net can have really high bandwidth!
Oh, absolutely! Nothing beats a train load of hard disks 😉
Even a single truck load beats fibre.
What throws me out is the requisite of throwing away the media after one use.
They want to remove any possibility of data leaving the private network. One can conceive of malware where, if present on the private network, could try to find ways to reach the outside. Disk drives could be contaminated just by mounting on a system. It happens in the Windows World all the time!
Just overwrite the media with random data on a non networked machine used solely for erasing media. Could run from a RO-DVD.
Certainly true, Carlos. But try explaining that to The PHB! Also, a strong prohibition about removing media makes the employees used to the policy, and eliminates the possibility of someone forgetting to scrub the disk. Regards, Lew
On 04/05/2024 20:14, Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure...
Any thoughts?
Regards, Lew
As Andrei said, the tool for this RMT. I have been using it for a few years to keep local copies of Leap repos:
rmt-cli repos custom list +-------------------+--------------------+---------------------------------------------------------------+---------------+--------------+-------------------------+
| ID | Name | URL | Mandatory? | Mirror? | Last Mirrored | +-------------------+--------------------+---------------------------------------------------------------+---------------+--------------+-------------------------+
| dist153oss | dist153oss | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ | Not Mandatory | Don't Mirror | 2023-04-20 01:40:44 UTC | | dist154oss | dist154oss | http://download.opensuse.org/distribution/leap/15.4/repo/oss/ | Not Mandatory | Mirror | 2024-05-05 04:08:43 UTC | | dist155oss | dist155oss | http://download.opensuse.org/distribution/leap/15.5/repo/oss/ | Not Mandatory | Mirror | 2024-05-05 04:19:12 UTC | | opensuse152dist | opensuse15.2dist | http://download.opensuse.org/distribution/leap/15.2/repo/oss/ | Not Mandatory | Don't Mirror | 2022-06-12 00:08:38 UTC | | opensuse152update | opensuse15.2update | http://download.opensuse.org/update/leap/15.2/oss/ | Not Mandatory | Don't Mirror | 2022-06-12 00:10:12 UTC | | tw_non-oss | tw_non-oss | http://download.opensuse.org/tumbleweed/repo/non-oss/ | Not Mandatory | Don't Mirror | 2024-02-08 06:30:03 UTC | | tw_oss | tw_oss | http://download.opensuse.org/tumbleweed/repo/oss/ | Not Mandatory | Don't Mirror | 2024-02-08 06:29:58 UTC | | tw_update | tw_update | http://download.opensuse.org/update/tumbleweed/ | Not Mandatory | Don't Mirror | | | updt153backports | updt153backports | http://download.opensuse.org/update/leap/15.3/backports/ | Not Mandatory | Don't Mirror | 2023-04-20 01:31:35 UTC | | updt153oss | updt153oss | http://download.opensuse.org/update/leap/15.3/oss/ | Not Mandatory | Don't Mirror | 2023-04-20 01:29:56 UTC | | updt153sle | updt153sle | http://download.opensuse.org/update/leap/15.3/sle/ | Not Mandatory | Don't Mirror | 2023-04-20 01:29:45 UTC | | updt154backports | updt154backports | http://download.opensuse.org/update/leap/15.4/backports/ | Not Mandatory | Mirror | 2024-05-05 04:10:25 UTC | | updt154oss | updt154oss | http://download.opensuse.org/update/leap/15.4/oss/ | Not Mandatory | Mirror | 2024-05-05 04:09:30 UTC | | updt154sle | updt154sle | http://download.opensuse.org/update/leap/15.4/sle/ | Not Mandatory | Mirror | 2024-05-05 04:14:59 UTC | | updt155backports | updt155backports | http://download.opensuse.org/update/leap/15.5/backports/ | Not Mandatory | Mirror | 2024-05-05 04:21:45 UTC | | updt155oss | updt155oss | http://download.opensuse.org/update/leap/15.5/oss/ | Not Mandatory | Mirror | 2024-05-05 04:20:04 UTC | | updt155sle | updt155sle | http://download.opensuse.org/update/leap/15.5/sle/ | Not Mandatory | Mirror | 2024-05-05 04:24:41 UTC | +-------------------+--------------------+---------------------------------------------------------------+---------------+--------------+-------------------------+
In the list above, I have included Tumbleweed but I do not mirror it yet - that's a future plan. Your use case for an air-gapped network is explicitly described with an example in section 4.7 of the RMT Guide, found here https://documentation.suse.com/sles/15-SP4/html/SLES-all/cha-rmt-mirroring.h... Yes, it did take a little figuring out but it works very reliably. Graham.
On 5/5/24 4:44 AM, Lew Wolfgang wrote:
Hi Folks,
Is there a way to maintain local copies of the openSUSE repositories? Maintenance includes keeping the local repos up-to-date by downloading only the deltas between the remote and local repos.
I know how to do this using the Red Hat "reposync" program, a part of the yum/dnf package, but it just doesn't feel right having to depend on Red Hat for what would appear to be core functionality.
Note: I can't use rsync due to policy constraints. But web ports 80 and 443 are okay. I know, go figure...
Any thoughts?
For Tumbleweed, delta's atleast are not possible, because we do not create deltarpm's there. For Leap updates this might be. It won't help with your air gap, unless its not really an air gap and your machine is network accessible to the ones you want to update. But for the interest of others on list I use https://github.com/Firstyear/opensuse-proxy-cache so that I only have to fetch tumbleweed updates once. Its a pretty easy podman container to setup. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 2024-05-07 12:32, Simon Lees wrote:
On 5/5/24 4:44 AM, Lew Wolfgang wrote:
...
It won't help with your air gap, unless its not really an air gap and your machine is network accessible to the ones you want to update. But for the interest of others on list I use https://github.com/Firstyear/opensuse-proxy-cache so that I only have to fetch tumbleweed updates once. Its a pretty easy podman container to setup.
I am impressed. :-o This may be what I have wanted to have for decades. But I don't understand how to install it, what I have to download and put where. I know nothing about podman or containers. wiki page, howto, perhaps? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
On 5/5/24 4:44 AM, Lew Wolfgang wrote:
...
It won't help with your air gap, unless its not really an air gap and your machine is network accessible to the ones you want to update. But for the interest of others on list I use https://github.com/Firstyear/opensuse-proxy-cache so that I only have to fetch tumbleweed updates once. Its a pretty easy podman container to setup.
I am impressed. :-o
This may be what I have wanted to have for decades.
But I don't understand how to install it, what I have to download and put where. I know nothing about podman or containers.
wiki page, howto, perhaps?
It really is as simple as described in the usage section (I chose podman over docker for reasons) docker run -p 8080:8080 -v /your/storage/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest I have mine in a systemd unit for convenience (You don't want the mirror chain option unless you want everything to come from an Australian location). Then just point your repos to http://127.0.0.1:8080 (or your IP Address) rather then http://download.opensuse.org In this case i'm storing my cached data in /data/osuse_cache because its mounted on a secondary drive. [Unit] Description=openSUSE Proxy Cache. [Service] Environment="MIRROR_CHAIN=https://mirrorcache-au.opensuse.org" ExecStart=podman run -e=$MIRROR_CHAIN -p 8080:8080 -v /data/osuse_cache/:/tmp/osuse_cache/ -u 1001:1001 firstyear/opensuse_proxy_cache:latest ExecStop=podman stop osuse_cache [Install] WantedBy=multi-user.target -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
On 5/5/24 4:44 AM, Lew Wolfgang wrote:
...
It won't help with your air gap, unless its not really an air gap and your machine is network accessible to the ones you want to update. But for the interest of others on list I use https://github.com/Firstyear/opensuse-proxy-cache so that I only have to fetch tumbleweed updates once. Its a pretty easy podman container to setup.
I am impressed. :-o
This may be what I have wanted to have for decades.
But I don't understand how to install it, what I have to download and put where. I know nothing about podman or containers.
wiki page, howto, perhaps?
It really is as simple as described in the usage section (I chose podman over docker for reasons)
docker run -p 8080:8080 -v /your/storage/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest
command not found :-) I suppose I have to install docker first. Does that docker download whatever it needs? Not stored locally?
I have mine in a systemd unit for convenience (You don't want the mirror chain option unless you want everything to come from an Australian location).
Then just point your repos to http://127.0.0.1:8080 (or your IP Address) rather then http://download.opensuse.org
In this case i'm storing my cached data in /data/osuse_cache because its mounted on a secondary drive.
I have to try this.
[Unit] Description=openSUSE Proxy Cache.
[Service] Environment="MIRROR_CHAIN=https://mirrorcache-au.opensuse.org" ExecStart=podman run -e=$MIRROR_CHAIN -p 8080:8080 -v /data/osuse_cache/:/tmp/osuse_cache/ -u 1001:1001 firstyear/opensuse_proxy_cache:latest ExecStop=podman stop osuse_cache
[Install] WantedBy=multi-user.target
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
It really is as simple as described in the usage section (I chose podman over docker for reasons)
docker run -p 8080:8080 -v /your/storage/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest
I take "/your/storage/" is the large disk space to store the cache. And "/tmp/osuse_cache/", what is it? I installed docker, which brought catatonit containerd criu docker docker-bash-completion docker-buildx docker-rootless-extras docker-zsh-completion fuse-overlayfs git-core git-gui git-web gitk libnet9 libsha1detectcoll1 libslirp0 perl-CGI perl-Error perl-Git python3-ipaddr python3-protobuf rootlesskit runc slirp4netns cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See 'docker run --help'. cer@Isengard:~> Running "systemctl start docker". cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'. cer@Isengard:~> Docker has to be run as root? Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest Unable to find image 'firstyear/opensuse_proxy_cache:latest' locally latest: Pulling from firstyear/opensuse_proxy_cache 9057b302fcfd: Pull complete fa32021715b2: Pull complete 1cd46f9ba906: Pull complete 7bb1a2809339: Pull complete b8bb2eabb8f0: Pull complete 428078d06f46: Pull complete a7de8e218dc2: Pull complete 0bd56b2411a0: Pull complete 8822301f7c75: Pull complete Digest: sha256:5c4fa25af847cc405bacf09415706053dcc7bb287fb25884ca47020cf1543efc Status: Downloaded newer image for firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user X: no matching entries in passwd file. ERRO[0015] error waiting for container: Isengard:~ # Huh, so what user must be that X? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-05-07 12:38, Carlos E. R. wrote:
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
It really is as simple as described in the usage section (I chose podman over docker for reasons)
docker run -p 8080:8080 -v /your/storage/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest
I take "/your/storage/" is the large disk space to store the cache. And "/tmp/osuse_cache/", what is it?
I installed docker, which brought
catatonit containerd criu docker docker-bash-completion docker-buildx docker-rootless-extras docker-zsh-completion fuse-overlayfs git-core git-gui git-web gitk libnet9 libsha1detectcoll1 libslirp0 perl-CGI perl-Error perl-Git python3-ipaddr python3-protobuf rootlesskit runc slirp4netns
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See 'docker run --help'. cer@Isengard:~>
Running "systemctl start docker".
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'. cer@Isengard:~>
I don't have docker installed, but all that suggests to me that there is a socket that needs to be opened first -- though I would have figured that the service file /should/ take care of that. What is the output of systemctl status docker.socket ?
Docker has to be run as root?
Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest Unable to find image 'firstyear/opensuse_proxy_cache:latest' locally latest: Pulling from firstyear/opensuse_proxy_cache 9057b302fcfd: Pull complete fa32021715b2: Pull complete 1cd46f9ba906: Pull complete 7bb1a2809339: Pull complete b8bb2eabb8f0: Pull complete 428078d06f46: Pull complete a7de8e218dc2: Pull complete 0bd56b2411a0: Pull complete 8822301f7c75: Pull complete Digest: sha256:5c4fa25af847cc405bacf09415706053dcc7bb287fb25884ca47020cf1543efc Status: Downloaded newer image for firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user X: no matching entries in passwd file. ERRO[0015] error waiting for container: Isengard:~ #
Huh, so what user must be that X?
On 2024-05-07 21:14, Darryl Gregorash wrote:
On 2024-05-07 12:38, Carlos E. R. wrote:
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
...
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See 'docker run --help'. cer@Isengard:~>
Running "systemctl start docker".
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'. cer@Isengard:~>
I don't have docker installed, but all that suggests to me that there is a socket that needs to be opened first -- though I would have figured that the service file /should/ take care of that.
What is the output of systemctl status docker.socket ?
No, it has to be run as root. I was trying as user. And then I have to create some user X. This thing needs more instructions.
Docker has to be run as root?
Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest Unable to find image 'firstyear/opensuse_proxy_cache:latest' locally latest: Pulling from firstyear/opensuse_proxy_cache 9057b302fcfd: Pull complete fa32021715b2: Pull complete 1cd46f9ba906: Pull complete 7bb1a2809339: Pull complete b8bb2eabb8f0: Pull complete 428078d06f46: Pull complete a7de8e218dc2: Pull complete 0bd56b2411a0: Pull complete 8822301f7c75: Pull complete Digest: sha256:5c4fa25af847cc405bacf09415706053dcc7bb287fb25884ca47020cf1543efc Status: Downloaded newer image for firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user X: no matching entries in passwd file. ERRO[0015] error waiting for container: Isengard:~ #
Huh, so what user must be that X?
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On Wednesday, 8 May 2024 04:55:51 ACST Carlos E. R. wrote:
On 2024-05-07 21:14, Darryl Gregorash wrote:
On 2024-05-07 12:38, Carlos E. R. wrote:
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
...
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See 'docker run --help'. cer@Isengard:~>
Running "systemctl start docker".
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'. cer@Isengard:~>
I don't have docker installed, but all that suggests to me that there is a socket that needs to be opened first -- though I would have figured that the service file /should/ take care of that.
What is the output of systemctl status docker.socket ?
No, it has to be run as root. I was trying as user.
And then I have to create some user X.
This thing needs more instructions. [...]
Add your username to the docker group. -- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================
On 5/8/24 4:08 AM, Carlos E. R. wrote:
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
It really is as simple as described in the usage section (I chose podman over docker for reasons)
docker run -p 8080:8080 -v /your/storage/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest
I take "/your/storage/" is the large disk space to store the cache. And "/tmp/osuse_cache/", what is it?
Whenever you see an option with a ":" its basically mapping something from your host system to something inside the container, so "/your/storage" on your physical machine gets mapped to "/tmp/osuse_cache/" inside the container.
I installed docker, which brought
catatonit containerd criu docker docker-bash-completion docker-buildx docker-rootless-extras docker-zsh-completion fuse-overlayfs git-core git-gui git-web gitk libnet9 libsha1detectcoll1 libslirp0 perl-CGI perl-Error perl-Git python3-ipaddr python3-protobuf rootlesskit runc slirp4netns
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. See 'docker run --help'. cer@Isengard:~>
Running "systemctl start docker".
cer@Isengard:~> docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'. cer@Isengard:~>
Docker has to be run as root?
It is possible to run some containers not as root, but you might need to be in the right group. I don't know if this is such a container I am also not a docker expert.
Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest Unable to find image 'firstyear/opensuse_proxy_cache:latest' locally latest: Pulling from firstyear/opensuse_proxy_cache 9057b302fcfd: Pull complete fa32021715b2: Pull complete 1cd46f9ba906: Pull complete 7bb1a2809339: Pull complete b8bb2eabb8f0: Pull complete 428078d06f46: Pull complete a7de8e218dc2: Pull complete 0bd56b2411a0: Pull complete 8822301f7c75: Pull complete Digest: sha256:5c4fa25af847cc405bacf09415706053dcc7bb287fb25884ca47020cf1543efc Status: Downloaded newer image for firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user X: no matching entries in passwd file. ERRO[0015] error waiting for container: Isengard:~ #
Huh, so what user must be that X?
Apparently in a past life I created a separate user "osuse_cache" that is just part of the "users" group, which on my system has the uid 1001, so I pass that in. In my case that user has permission to read and write to "/your/storage/" -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 2024-05-08 03:39, Simon Lees wrote:
On 5/8/24 4:08 AM, Carlos E. R. wrote:
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
...
Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest Unable to find image 'firstyear/opensuse_proxy_cache:latest' locally latest: Pulling from firstyear/opensuse_proxy_cache 9057b302fcfd: Pull complete fa32021715b2: Pull complete 1cd46f9ba906: Pull complete 7bb1a2809339: Pull complete b8bb2eabb8f0: Pull complete 428078d06f46: Pull complete a7de8e218dc2: Pull complete 0bd56b2411a0: Pull complete 8822301f7c75: Pull complete Digest: sha256:5c4fa25af847cc405bacf09415706053dcc7bb287fb25884ca47020cf1543efc Status: Downloaded newer image for firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user X: no matching entries in passwd file. ERRO[0015] error waiting for container: Isengard:~ #
Huh, so what user must be that X?
Apparently in a past life I created a separate user "osuse_cache" that is just part of the "users" group, which on my system has the uid 1001, so I pass that in. In my case that user has permission to read and write to "/your/storage/"
Ok, then I understand I should create a user that owns the storage, and give that user as "-u that_user:that_user"? Or something else? :-? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 5/8/24 8:50 PM, Carlos E. R. wrote:
On 2024-05-08 03:39, Simon Lees wrote:
On 5/8/24 4:08 AM, Carlos E. R. wrote:
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
...
Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u X:X firstyear/opensuse_proxy_cache:latest Unable to find image 'firstyear/opensuse_proxy_cache:latest' locally latest: Pulling from firstyear/opensuse_proxy_cache 9057b302fcfd: Pull complete fa32021715b2: Pull complete 1cd46f9ba906: Pull complete 7bb1a2809339: Pull complete b8bb2eabb8f0: Pull complete 428078d06f46: Pull complete a7de8e218dc2: Pull complete 0bd56b2411a0: Pull complete 8822301f7c75: Pull complete Digest: sha256:5c4fa25af847cc405bacf09415706053dcc7bb287fb25884ca47020cf1543efc Status: Downloaded newer image for firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user X: no matching entries in passwd file. ERRO[0015] error waiting for container: Isengard:~ #
Huh, so what user must be that X?
Apparently in a past life I created a separate user "osuse_cache" that is just part of the "users" group, which on my system has the uid 1001, so I pass that in. In my case that user has permission to read and write to "/your/storage/"
Ok, then I understand I should create a user that owns the storage, and give that user as "-u that_user:that_user"?
Yep, where that_user is the users uid -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 2024-05-09 03:10, Simon Lees wrote:
On 5/8/24 8:50 PM, Carlos E. R. wrote:
On 2024-05-08 03:39, Simon Lees wrote:
On 5/8/24 4:08 AM, Carlos E. R. wrote:
On 2024-05-07 15:56, Simon Lees wrote:
On 5/7/24 9:27 PM, Carlos E. R. wrote:
On 2024-05-07 12:32, Simon Lees wrote:
...
Huh, so what user must be that X?
Apparently in a past life I created a separate user "osuse_cache" that is just part of the "users" group, which on my system has the uid 1001, so I pass that in. In my case that user has permission to read and write to "/your/storage/"
Ok, then I understand I should create a user that owns the storage, and give that user as "-u that_user:that_user"?
Yep, where that_user is the users uid
I have now directory /data/hoard_2/osuse_cache/ owned by user osuse_cache. Tested that the user can write there. Still no go: Isengard:/data/hoard_2/osuse_cache # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u osuse_cache:osuse_cache firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user osuse_cache: no matching entries in passwd file. ERRO[0000] error waiting for container: Isengard:/data/hoard_2/osuse_cache # tail /etc/passwd | grep osuse osuse_cache:x:1200:100:osuse_cache:/home/osuse_cache:/bin/bash Isengard:/data/hoard_2/osuse_cache # I log out and in, so that the root user rereads the passwd file. Still no go: Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u osuse_cache:osuse_cache firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user osuse_cache: no matching entries in passwd file. ERRO[0000] error waiting for container: Isengard:~ # I restart the docker service. No go. Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u osuse_cache:osuse_cache firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user osuse_cache: no matching entries in passwd file. ERRO[0000] error waiting for container: Isengard:~ # Changing name of the user osuse_cache, to remove the "_". Still no go. Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u osusecache:osusecache firstyear/opensuse_proxy_cache:latest docker: Error response from daemon: unable to find user osusecache: no matching entries in passwd file. ERRO[0000] error waiting for container: Isengard:~ # Stumbled. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On Fri, 10 May 2024 13:49:16 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
Yep, where that_user is the users uid
I have now directory /data/hoard_2/osuse_cache/ owned by user osuse_cache. Tested that the user can write there. Still no go:
Isengard:/data/hoard_2/osuse_cache # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u osuse_cache:osuse_cache
Did you read what Simon wrote? UID!
On 2024-05-10 14:35, Dave Howorth wrote:
On Fri, 10 May 2024 13:49:16 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
Yep, where that_user is the users uid
I have now directory /data/hoard_2/osuse_cache/ owned by user osuse_cache. Tested that the user can write there. Still no go:
Isengard:/data/hoard_2/osuse_cache # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u osuse_cache:osuse_cache
Did you read what Simon wrote? UID!
I thought it was a typo. Isengard:~ # docker run -p 8080:8080 -v /data/hoard_2/osuse_cache/:/tmp/osuse_cache/ -u 1200:1200 firstyear/opensuse_proxy_cache:latest Isengard:~ # Is it running? Isengard:~ # ps afxu | grep docker root 13292 0.0 0.0 5644 816 pts/29 S+ 14:50 0:00 | \_ grep --color=auto docker root 5256 0.0 1.1 1843648 88184 ? Ssl 13:36 0:01 /usr/bin/dockerd --add-runtime oci=/usr/sbin/docker-runc root 5264 0.1 0.6 1949256 49148 ? Ssl 13:36 0:06 \_ containerd --config /var/run/docker/containerd/containerd.toml --log-level warn Isengard:~ # trying. links 127.0.0.1:8080 Error loading http://127.0.0.1:8080/: Connection refused Doesn't work. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
participants (8)
-
Andrei Borzenkov -
Carlos E. R. -
Darryl Gregorash -
Dave Howorth -
G McAlister -
Lew Wolfgang -
Rodney Baker -
Simon Lees