Re: [gentoo-user] Docker installation issues

[Andreas Fink]

On Sat, 10 Dec 2022 15:51:17 -0500
Mansour Al Akeel  wrote:

> Andreas,
> 
> Thank you very much. In fact I didn't go that deep yet, and not sure if I
> should. I just found that the url is not accessible even from a browser.
> Googling a bit, tells me there is no clear URL for docker-registry and
> possibly this one is outdated. I will continue looking around to confirm
> what the current default repo should be. If you have any suggestions,
> please let me know.
> 
> 
>  localhost in ~
> ○ → curl -k -v https://registry-1.docker.io/v2/
> *   Trying 34.228.211.243:443...
> 
> * connect to 34.228.211.243 port 443 failed: Connection timed out
> * Failed to connect to registry-1.docker.io port 443 after 129401 ms:
> Couldn't connect to server
> * Closing connection 0
> curl: (28) Failed to connect to registry-1.docker.io port 443 after 129401
> ms: Couldn't connect to server


You have a a strange DNS resolution. The IP address 34.227.211.243
seems wrong. Here is what I see when I look at the DNS records:
andreas@localhost ~$ dig registry-1.docker.io

; <<>> DiG 9.16.33 <<>> registry-1.docker.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11419
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;registry-1.docker.io.  IN  A

;; ANSWER SECTION:
registry-1.docker.io.   13  IN  A   34.205.13.154
registry-1.docker.io.   13  IN  A   44.205.64.79
registry-1.docker.io.   13  IN  A   3.216.34.172

;; Query time: 10 msec
;; SERVER: 79.143.183.251#53(79.143.183.251)
;; WHEN: Sun Dec 11 06:56:50 CET 2022
;; MSG SIZE  rcvd: 97

I am not sure
Not sure where you get the wrong IP from, but it is a DNS issue.

Re: [gentoo-user] NAS and replacing with larger drives

[David Rosenbaum]

Thanks

Dave

On Sat, Dec 10, 2022, 11:19 AM Frank Steinmetzger  wrote:

> Am Sat, Dec 10, 2022 at 09:20:17AM + schrieb Wols Lists:
>
> > > > Depending on the PVR make/model I've seen 1080p resolution
> recordings with
> > > > .m2ts and .ts file extensions, while the codecs inside them are the
> same.
> -^^^
> >
> > > I wasn’t aware that ts could contain h264. But then again—I never
> really
> -^^^
> > > bothered with live TV recordings in recent years.
>
> > I think this is confusing CONTAINER and CODEC.
>
> Where do we confuse those two? We specifically talked of codecs and
> “contain”.
>
> > .ts is a container format, h264 is a codec. I don't understand it myself,
> > either but think of ts as your directory structure and h264 as your file
> > structure.
>
> Now you are confusing me. You say you don’t understand it, but then explain
> it. TS is like AVI and MKV: a file structure for the payload data. And
> payload data can be all kinds of stuff, from ASS plaintext subtitles, over
> opus audio to mpeg2 or h264 video.
>
> > Incidentally, sticking this stuff in a .tar is probably okay - that's
> just
> > another container, but sticking it in a .tar.gz is not, the gz is your
> codec
> > and will make the file BIGGER in all probability.
>
> Tar does not compress, it simply puts all inputs in a 1:1 stream. It does
> add some metadata (filename and so on). Packers reduce data volume by
> increasing information-per-byte. So if the total information stays the same
> (for lossless coding), the number of bytes decreases. Encoded video data
> ideally has even entropy. It is indistinguishable from random noise. That’s
> why compressing it again does not yield anything, or even adds some volume
> again.
>
> --
> Grüße | Greetings | Salut | Qapla’
> Please do not share anything from, with or about me on any social network.
>
> “Mankind must put an end to war or war will put an end to mankind.”
>  – John F. Kennedy
>

Re: [gentoo-user] NAS and replacing with larger drives

[David Rosenbaum]

Can I get sum help with privacy an control of my ph.

David

On Sat, Dec 10, 2022, 9:49 PM David Rosenbaum 
wrote:

> Tanks
>
> Dave
>
> On Sat, Dec 10, 2022, 9:46 PM David Rosenbaum 
> wrote:
>
>>
>>
>> Dave
>>
>> On Sat, Dec 10, 2022, 4:28 PM Mark Knecht  wrote:
>>
>>>
>>>
>>> On Sat, Dec 10, 2022 at 1:42 PM Dale  wrote:
>>> 
>>> > It does appear that several people are making it so NAS boxes can be
>>> > easily built by us nerdy types and not be huge.  Things are a bit
>>> > interesting right now for hardware and such.  Some parts are expensive,
>>> > hard to find or just plain unavailable.  Still, I suspect that this
>>> will
>>> > get better later on.  The good thing, people are working on this. There
>>> > is interest in having a option.
>>> >
>>>
>>> I know I've said this before but yes, people are working on it and it
>>> is buildable by people like us.
>>>
>>> https://www.truenas.com/truenas-core/
>>>
>>> Any old x64 PC and a few disks will get you up and running. It's
>>> open source as much as BSD is open source. It's not Linux
>>> so there was a little learning to do but it wasn't bad.
>>>
>>> Mine has a small SSD as the boot drive and then RAID1 pairs
>>> running OpenZFS for storage. It's inexpensive if you have an
>>> old computer to build on.
>>>
>>> Good luck,
>>> Mark
>>>
>>

Re: [gentoo-user] NAS and replacing with larger drives

[Dale]

Mark Knecht wrote:
> 
> >
> > I got a old rig I can use.  I actually burned OpenNAS, TrueNAS or
> FreeNAS on a USB stick.  I can't recall which one I put on it tho.  I
> downloaded all three.  lol  If you know that one is better than the
> others, feel free to share.  Also, I'd like to keep using LVM if I
> can.  If nothing else, I already got the data on the drives and won't
> have to reformat and copy again.  It took almost 100 hours to copy to
> the new 16TB drive.  Using LVM would make that easier, and faster.
> >
> > I'll have to work with what I got for now but I really like the
> Raspberry option for its size and good options to upgrade later.  I'll
> just make do with something else until that option is doable.  Maybe
> it won't be to long.
> >
> > Dale
> >
> > :-)  :-)
>
> TrueNAS Core. It's the free one. Works great. Very stable, but it is
> BSD, not Linux so you'll be frustrated sometimes. None the less it
> works very well.


Well, I booted it and it is FreeNAS.  I got it on a USB stick tho. 
Well, I put the installer on one stick and then installed on a second
stick.  Kinda odd but I get it.  I also noticed it is BSD based.  I
played with BSD once before.  One thing I can say, it's secure.  Big time.

I see it uses ZFS or something.  No mention of LVM.  I figured that.  Oh
well. 

If I can't hammer FreeNAS into shape, I'll try TrueNAS next.  If it
works, that's fine too.  ;-) 

Thanks.

Dale

:-)  :-) 

P. S.  When I first booted, I didn't have the ethernet plugged in.  It
wasn't happy about that.  Given it is NAS software, I should have known
better.  ROFL 

Re: [gentoo-user] NAS and replacing with larger drives

[Mark Knecht]

>
> I got a old rig I can use.  I actually burned OpenNAS, TrueNAS or FreeNAS
on a USB stick.  I can't recall which one I put on it tho.  I downloaded
all three.  lol  If you know that one is better than the others, feel free
to share.  Also, I'd like to keep using LVM if I can.  If nothing else, I
already got the data on the drives and won't have to reformat and copy
again.  It took almost 100 hours to copy to the new 16TB drive.  Using LVM
would make that easier, and faster.
>
> I'll have to work with what I got for now but I really like the Raspberry
option for its size and good options to upgrade later.  I'll just make do
with something else until that option is doable.  Maybe it won't be to
long.
>
> Dale
>
> :-)  :-)

TrueNAS Core. It's the free one. Works great. Very stable, but it is BSD,
not Linux so you'll be frustrated sometimes. None the less it works very
well.

Re: [gentoo-user] NAS and replacing with larger drives

[David Rosenbaum]

Tanks

Dave

On Sat, Dec 10, 2022, 9:46 PM David Rosenbaum 
wrote:

>
>
> Dave
>
> On Sat, Dec 10, 2022, 4:28 PM Mark Knecht  wrote:
>
>>
>>
>> On Sat, Dec 10, 2022 at 1:42 PM Dale  wrote:
>> 
>> > It does appear that several people are making it so NAS boxes can be
>> > easily built by us nerdy types and not be huge.  Things are a bit
>> > interesting right now for hardware and such.  Some parts are expensive,
>> > hard to find or just plain unavailable.  Still, I suspect that this will
>> > get better later on.  The good thing, people are working on this. There
>> > is interest in having a option.
>> >
>>
>> I know I've said this before but yes, people are working on it and it
>> is buildable by people like us.
>>
>> https://www.truenas.com/truenas-core/
>>
>> Any old x64 PC and a few disks will get you up and running. It's
>> open source as much as BSD is open source. It's not Linux
>> so there was a little learning to do but it wasn't bad.
>>
>> Mine has a small SSD as the boot drive and then RAID1 pairs
>> running OpenZFS for storage. It's inexpensive if you have an
>> old computer to build on.
>>
>> Good luck,
>> Mark
>>
>

Re: [gentoo-user] NAS and replacing with larger drives

[David Rosenbaum]

Dave

On Sat, Dec 10, 2022, 4:28 PM Mark Knecht  wrote:

>
>
> On Sat, Dec 10, 2022 at 1:42 PM Dale  wrote:
> 
> > It does appear that several people are making it so NAS boxes can be
> > easily built by us nerdy types and not be huge.  Things are a bit
> > interesting right now for hardware and such.  Some parts are expensive,
> > hard to find or just plain unavailable.  Still, I suspect that this will
> > get better later on.  The good thing, people are working on this. There
> > is interest in having a option.
> >
>
> I know I've said this before but yes, people are working on it and it
> is buildable by people like us.
>
> https://www.truenas.com/truenas-core/
>
> Any old x64 PC and a few disks will get you up and running. It's
> open source as much as BSD is open source. It's not Linux
> so there was a little learning to do but it wasn't bad.
>
> Mine has a small SSD as the boot drive and then RAID1 pairs
> running OpenZFS for storage. It's inexpensive if you have an
> old computer to build on.
>
> Good luck,
> Mark
>

Re: [gentoo-user] NAS and replacing with larger drives

[Dale]

Mark Knecht wrote:
>
>
> On Sat, Dec 10, 2022 at 1:42 PM Dale  > wrote:
> 
> > It does appear that several people are making it so NAS boxes can be
> > easily built by us nerdy types and not be huge.  Things are a bit
> > interesting right now for hardware and such.  Some parts are expensive,
> > hard to find or just plain unavailable.  Still, I suspect that this will
> > get better later on.  The good thing, people are working on this. There
> > is interest in having a option.
> >
>
> I know I've said this before but yes, people are working on it and it
> is buildable by people like us.
>
> https://www.truenas.com/truenas-core/
>
> Any old x64 PC and a few disks will get you up and running. It's 
> open source as much as BSD is open source. It's not Linux
> so there was a little learning to do but it wasn't bad.
>
> Mine has a small SSD as the boot drive and then RAID1 pairs
> running OpenZFS for storage. It's inexpensive if you have an 
> old computer to build on.
>
> Good luck,
> Mark

I got a old rig I can use.  I actually burned OpenNAS, TrueNAS or
FreeNAS on a USB stick.  I can't recall which one I put on it tho.  I
downloaded all three.  lol  If you know that one is better than the
others, feel free to share.  Also, I'd like to keep using LVM if I can. 
If nothing else, I already got the data on the drives and won't have to
reformat and copy again.  It took almost 100 hours to copy to the new
16TB drive.  Using LVM would make that easier, and faster.

I'll have to work with what I got for now but I really like the
Raspberry option for its size and good options to upgrade later.  I'll
just make do with something else until that option is doable.  Maybe it
won't be to long. 

Dale

:-)  :-) 

Re: [gentoo-user] NAS and replacing with larger drives

[Mark Knecht]

On Sat, Dec 10, 2022 at 1:42 PM Dale  wrote:

> It does appear that several people are making it so NAS boxes can be
> easily built by us nerdy types and not be huge.  Things are a bit
> interesting right now for hardware and such.  Some parts are expensive,
> hard to find or just plain unavailable.  Still, I suspect that this will
> get better later on.  The good thing, people are working on this. There
> is interest in having a option.
>

I know I've said this before but yes, people are working on it and it
is buildable by people like us.

https://www.truenas.com/truenas-core/

Any old x64 PC and a few disks will get you up and running. It's
open source as much as BSD is open source. It's not Linux
so there was a little learning to do but it wasn't bad.

Mine has a small SSD as the boot drive and then RAID1 pairs
running OpenZFS for storage. It's inexpensive if you have an
old computer to build on.

Good luck,
Mark

Re: [gentoo-user] Docker installation issues

[Mansour Al Akeel]

Andreas,

Thank you very much. In fact I didn't go that deep yet, and not sure if I
should. I just found that the url is not accessible even from a browser.
Googling a bit, tells me there is no clear URL for docker-registry and
possibly this one is outdated. I will continue looking around to confirm
what the current default repo should be. If you have any suggestions,
please let me know.


 localhost in ~
○ → curl -k -v https://registry-1.docker.io/v2/
*   Trying 34.228.211.243:443...

* connect to 34.228.211.243 port 443 failed: Connection timed out
* Failed to connect to registry-1.docker.io port 443 after 129401 ms:
Couldn't connect to server
* Closing connection 0
curl: (28) Failed to connect to registry-1.docker.io port 443 after 129401
ms: Couldn't connect to server





On Sat, Dec 10, 2022 at 1:32 PM Andreas Fink  wrote:

> On Sat, 10 Dec 2022 12:30:40 -0500
> Mansour Al Akeel  wrote:
>
> > I am using Openrc
> >
> > This was my initial /etc/conf.d/docker
> > DOCKER_OPTS="--storage-driver overlay2 --data-root /srv/var/lib/docker"
> >
> > when I try:
> >
> > $ docker pull hello-world
> >
> > Error response from daemon: Get "https://registry-1.docker.io/v2/":
> > net/http: request canceled while waiting for connection (Client.Timeout
> > exceeded while awaiting headers)
> >
> > Trying to troubleshoot:
> >
> > localhost /home/mansour # tail -n 20 /var/log/docker.log
> > time="2022-12-10T12:17:03.473550705-05:00" level=info msg="scheme
> \"unix\"
> > not registered, fallback to default scheme" module=grpc
> > time="2022-12-10T12:17:03.473566413-05:00" level=info
> > msg="ccResolverWrapper: sending update to cc:
> > {[{unix:///run/containerd/containerd.sock   0 }]  }"
> > module=grpc
> > time="2022-12-10T12:17:03.473573787-05:00" level=info msg="ClientConn
> > switching balancer to \"pick_first\"" module=grpc
> > time="2022-12-10T12:17:03.474530993-05:00" level=info msg="parsed scheme:
> > \"unix\"" module=grpc
> > time="2022-12-10T12:17:03.474545549-05:00" level=info msg="scheme
> \"unix\"
> > not registered, fallback to default scheme" module=grpc
> > time="2022-12-10T12:17:03.474563752-05:00" level=info
> > msg="ccResolverWrapper: sending update to cc:
> > {[{unix:///run/containerd/containerd.sock   0 }]  }"
> > module=grpc
> > time="2022-12-10T12:17:03.474571186-05:00" level=info msg="ClientConn
> > switching balancer to \"pick_first\"" module=grpc
> > time="2022-12-10T12:17:03.478908716-05:00" level=warning msg="Your kernel
> > does not support cgroup blkio weight"
> > time="2022-12-10T12:17:03.478927115-05:00" level=warning msg="Your kernel
> > does not support cgroup blkio weight_device"
> > time="2022-12-10T12:17:03.479037897-05:00" level=info msg="Loading
> > containers: start."
> > time="2022-12-10T12:17:03.495743563-05:00" level=info msg="failed to read
> > ipv6 net.ipv6.conf..accept_ra" bridge=docker0
> > syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
> > time="2022-12-10T12:17:03.518761943-05:00" level=info msg="Default bridge
> > (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option
> --bip
> > can be used to set a preferred IP address"
> > time="2022-12-10T12:17:03.518886881-05:00" level=info msg="failed to read
> > ipv6 net.ipv6.conf..accept_ra" bridge=docker0
> > syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
> > time="2022-12-10T12:17:03.534616741-05:00" level=info msg="Loading
> > containers: done."
> > time="2022-12-10T12:17:03.541080189-05:00" level=info msg="Docker daemon"
> > commit=a89b84221c graphdriver(s)=overlay2 version=20.10.17
> > time="2022-12-10T12:17:03.541122352-05:00" level=info msg="Daemon has
> > completed initialization"
> > time="2022-12-10T12:17:03.549888103-05:00" level=info msg="API listen on
> > /var/run/docker.sock"
> > time="2022-12-10T12:17:27.025622231-05:00" level=warning msg="Error
> getting
> > v2 registry: Get \"https://registry-1.docker.io/v2/\": net/http: request
> > canceled while waiting for connection (Client.Timeout exceeded while
> > awaiting headers)"
> > time="2022-12-10T12:17:27.025667054-05:00" level=info msg="Attempting
> next
> > endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\":
> > net/http: request canceled while waiting for connection (Client.Timeout
> > exceeded while awaiting headers)"
> > time="2022-12-10T12:17:27.026851821-05:00" level=error msg="Handler for
> > POST /v1.41/images/create returned error: Get \"
> > https://registry-1.docker.io/v2/\": net/http: request canceled while
> > waiting for connection (Client.Timeout exceeded while awaiting headers)"
> >
> > time="2022-12-10T12:15:42.036053086-05:00" level=info msg="loading plugin
> > \"io.containerd.internal.v1.tracing\"..." type=io.containerd.internal.v1
> > time="2022-12-10T12:15:42.036068412-05:00" level=error msg="failed to
> > initialize a tracing processor \"otlp\"" error="no OpenTelemetry
> endpoint:
> > skip plugin"
> > time="2022-12-10T12:15:42.036100189-05:00" level=info msg="loading plugin
> > 

Re: [gentoo-user] NAS and replacing with larger drives

[Dale]

Dale wrote:
> Howdy,
>
> I've pretty much reached a limit on my backups.  I'm up to a 16TB hard
> drive for one and even that won't last long.  Larger drives are much
> more costly.  A must have NAS is quickly approaching.  I've been
> searching around and find some things confusing.  I'm hoping someone can
> clear up that confusion.  I'm also debating what path to travel down. 
> I'd also like to keep costs down as well.  That said, I don't mind
> paying a little more for one that would offer a much better option. 
>
> Path one, buy a NAS, possibly used, that has no drives.  If possible, I
> may even replace the OS that comes on it or upgrade if I can.  I'm not
> looking for fancy, or even RAID.  Just looking for a two bay NAS that
> will work.  First, what is a DAS?  Is that totally different than a
> NAS?  From what I've found, a DAS is not what I'm looking for since I
> want a ethernet connection and the ability to control things over the
> network.  It seems DAS lacks that feature but not real sure.  I'm not
> sure I can upgrade the software/OS on a DAS either. 
>
> Next thing.  Let's say a NAS comes with two 4TB drives for a total of
> 8TB of capacity from the factory, using LVM or similar software I
> assume.  Is that limited to that capacity or can I for example replace
> one or both drives with for example 14TB drives for a total of 28TBs of
> capacity?  If one does that, let's say it uses LVM, can I somehow move
> data as well or is that beyond the abilities of a NAS?  Could it be done
> inside my computer for example?  Does this vary by brand or even model? 
>
> Path two, I've researched building a NAS using a Raspberry Pi 4 8GB as
> another option.  They come as parts, cases too, but the newer and faster
> models of Raspberry Pi 4 with more ram seem to work pretty well.  The
> old slower models with small amounts of ram don't fair as well.  While I
> want a descent speed, I'm not looking for or expecting it to be
> blazingly fast.  I just wonder, if from a upgrade and expansion point of
> view, if building a NAS would be better.  I've also noticed, it seems
> all Raspberry things come with a display port.  That means I could hook
> up a monitor and mouse/keyboard when needed.  That could be a bonus. 
> Heck, I may can even put some sort of Gentoo on that thing.  :-D
>
> One reason I'm wanting to go this route, I'm trying to keep it small and
> able to fit inside my fire safe.  I plan to buy a media type safe that
> is larger but right now, it needs to fit inside my current safe.  Most
> of the 2 bay NAS or a Raspberry Pi based NAS are fairly small.  They not
> much bigger than the three external hard drives and a couple bare drives
> that currently occupy my safe. 
>
> One thing I'd like to have no matter what path I go down, the ability to
> encrypt the data.  My current backup drives are encrypted and I'd like
> to keep it that way.  If that is possible to do.  I suspect the
> Raspberry option would since I'd control the OS/software placed on it. 
> I could be wrong tho. 
>
> One last thing.  Are there any NAS type boxes that I should absolutely
> avoid if I go that route?  Maybe it is a model that has serious
> limitations or has other problems.  I think the DAS thing may be one for
> me to avoid but I'm not for sure what limits it has.  Google didn't help
> a lot. It also could be as simple as, avoid any model that says this in
> the description or uses some type of software that is bad or limits
> options. 
>
> Thoughts?  Info to share?  Ideas on a best path forward?  Buy already
> built or build?
>
> Thanks.
>
> Dale
>
> :-)  :-) 
>

It does appear that several people are making it so NAS boxes can be
easily built by us nerdy types and not be huge.  Things are a bit
interesting right now for hardware and such.  Some parts are expensive,
hard to find or just plain unavailable.  Still, I suspect that this will
get better later on.  The good thing, people are working on this. There
is interest in having a option. 

I may in the meantime have to split up my large directory and the
resulting backup.  Split it in half or something.  I just bought a 16TB
hard drive.  It's over 90% full already.  That said, my downloading is
slowing down quite a lot.  It will last a while.  I may setup a old
system as a NAS and just keep it in a outbuilding for the time being. 
Should offer me some protection at least.

If anyone runs up on some info that might relate to this, please share. 
Maybe something new will come out that we don't know about now. If I do
build something, I'll likely post and share what I used, how much effort
was involved and the end results. Maybe this will help others as well.

Thanks.

Dale

:-)  :-)

P. S.  I currently have a spare 14TB, 8TB and 6TB hard drive not in
use.  That's 28TBs available.  That's a good start on a NAS as far as
drives go.  Currently in use in external enclosures for backups, 16Tb,
8TB and a 6TB hard drive. 

Re: [gentoo-user] Docker installation issues

[Andreas Fink]

On Sat, 10 Dec 2022 12:30:40 -0500
Mansour Al Akeel  wrote:

> I am using Openrc
>
> This was my initial /etc/conf.d/docker
> DOCKER_OPTS="--storage-driver overlay2 --data-root /srv/var/lib/docker"
>
> when I try:
>
> $ docker pull hello-world
>
> Error response from daemon: Get "https://registry-1.docker.io/v2/":
> net/http: request canceled while waiting for connection (Client.Timeout
> exceeded while awaiting headers)
>
> Trying to troubleshoot:
>
> localhost /home/mansour # tail -n 20 /var/log/docker.log
> time="2022-12-10T12:17:03.473550705-05:00" level=info msg="scheme \"unix\"
> not registered, fallback to default scheme" module=grpc
> time="2022-12-10T12:17:03.473566413-05:00" level=info
> msg="ccResolverWrapper: sending update to cc:
> {[{unix:///run/containerd/containerd.sock   0 }]  }"
> module=grpc
> time="2022-12-10T12:17:03.473573787-05:00" level=info msg="ClientConn
> switching balancer to \"pick_first\"" module=grpc
> time="2022-12-10T12:17:03.474530993-05:00" level=info msg="parsed scheme:
> \"unix\"" module=grpc
> time="2022-12-10T12:17:03.474545549-05:00" level=info msg="scheme \"unix\"
> not registered, fallback to default scheme" module=grpc
> time="2022-12-10T12:17:03.474563752-05:00" level=info
> msg="ccResolverWrapper: sending update to cc:
> {[{unix:///run/containerd/containerd.sock   0 }]  }"
> module=grpc
> time="2022-12-10T12:17:03.474571186-05:00" level=info msg="ClientConn
> switching balancer to \"pick_first\"" module=grpc
> time="2022-12-10T12:17:03.478908716-05:00" level=warning msg="Your kernel
> does not support cgroup blkio weight"
> time="2022-12-10T12:17:03.478927115-05:00" level=warning msg="Your kernel
> does not support cgroup blkio weight_device"
> time="2022-12-10T12:17:03.479037897-05:00" level=info msg="Loading
> containers: start."
> time="2022-12-10T12:17:03.495743563-05:00" level=info msg="failed to read
> ipv6 net.ipv6.conf..accept_ra" bridge=docker0
> syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
> time="2022-12-10T12:17:03.518761943-05:00" level=info msg="Default bridge
> (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip
> can be used to set a preferred IP address"
> time="2022-12-10T12:17:03.518886881-05:00" level=info msg="failed to read
> ipv6 net.ipv6.conf..accept_ra" bridge=docker0
> syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
> time="2022-12-10T12:17:03.534616741-05:00" level=info msg="Loading
> containers: done."
> time="2022-12-10T12:17:03.541080189-05:00" level=info msg="Docker daemon"
> commit=a89b84221c graphdriver(s)=overlay2 version=20.10.17
> time="2022-12-10T12:17:03.541122352-05:00" level=info msg="Daemon has
> completed initialization"
> time="2022-12-10T12:17:03.549888103-05:00" level=info msg="API listen on
> /var/run/docker.sock"
> time="2022-12-10T12:17:27.025622231-05:00" level=warning msg="Error getting
> v2 registry: Get \"https://registry-1.docker.io/v2/\": net/http: request
> canceled while waiting for connection (Client.Timeout exceeded while
> awaiting headers)"
> time="2022-12-10T12:17:27.025667054-05:00" level=info msg="Attempting next
> endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\":
> net/http: request canceled while waiting for connection (Client.Timeout
> exceeded while awaiting headers)"
> time="2022-12-10T12:17:27.026851821-05:00" level=error msg="Handler for
> POST /v1.41/images/create returned error: Get \"
> https://registry-1.docker.io/v2/\": net/http: request canceled while
> waiting for connection (Client.Timeout exceeded while awaiting headers)"
>
> time="2022-12-10T12:15:42.036053086-05:00" level=info msg="loading plugin
> \"io.containerd.internal.v1.tracing\"..." type=io.containerd.internal.v1
> time="2022-12-10T12:15:42.036068412-05:00" level=error msg="failed to
> initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint:
> skip plugin"
> time="2022-12-10T12:15:42.036100189-05:00" level=info msg="loading plugin
> \"io.containerd.grpc.v1.cri\"..." type=io.containerd.grpc.v1
> time="2022-12-10T12:15:42.036390695-05:00" level=info msg="Start cri plugin
> with config {PluginConfig:{ContainerdConfig:{Snapshotter:overlayfs
> DefaultRuntimeName:runc DefaultRuntime:{Type: Path: Engine:
> PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[]
> PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir:
> NetworkPluginMaxConfNum:0} UntrustedWorkloadRuntime:{Type: Path: Engine:
> PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[]
> PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir:
> NetworkPluginMaxConfNum:0} Runtimes:map[runc:{Type:io.containerd.runc.v2
> Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root:
> Options:map[BinaryName: CriuImagePath: CriuPath: CriuWorkPath: IoGid:0
> IoUid:0 NoNewKeyring:false NoPivotRoot:false Root: ShimCgroup:
> SystemdCgroup:false] PrivilegedWithoutHostDevices:false BaseRuntimeSpec:
> NetworkPluginConfDir: NetworkPluginMaxConfNum:0}] 

Re: [gentoo-user] NAS and replacing with larger drives

[David Rosenbaum]

Someone has hacked my ph.im 44 years old an pay for every thing.house car
an wifi

Dave

On Sat, Dec 10, 2022, 12:28 PM Michael  wrote:

> On Saturday, 10 December 2022 16:30:03 GMT Wols Lists wrote:
> > On 10/12/2022 16:19, Frank Steinmetzger wrote:
> > > Where do we confuse those two? We specifically talked of codecs and
> > > “contain”.
> >
> > "I didn't know .ts could contain h264".
> >
> > If .ts is the container, then surely the assumption is it can contain
> > any codec? If not, why not?
>
> Not any codec.  Some container formats are only compatible with certain
> codecs, or rather the other way around.  Have a look here:
>
> https://en.wikipedia.org/wiki/Comparison_of_video_container_formats
>
> I suppose the answer to 'why not' boils down to the whatever structure and
> data the container format is designed to be compatible with, but I don't
> know
> more than this.
>
>
> https://en.wikipedia.org/wiki/File:Informatik-Containerformate-Beispiele.svg
>
>

[gentoo-user] Docker installation issues

[Mansour Al Akeel]

I am using Openrc

This was my initial /etc/conf.d/docker
DOCKER_OPTS="--storage-driver overlay2 --data-root /srv/var/lib/docker"

when I try:

$ docker pull hello-world

Error response from daemon: Get "https://registry-1.docker.io/v2/":
net/http: request canceled while waiting for connection (Client.Timeout
exceeded while awaiting headers)

Trying to troubleshoot:

localhost /home/mansour # tail -n 20 /var/log/docker.log
time="2022-12-10T12:17:03.473550705-05:00" level=info msg="scheme \"unix\"
not registered, fallback to default scheme" module=grpc
time="2022-12-10T12:17:03.473566413-05:00" level=info
msg="ccResolverWrapper: sending update to cc:
{[{unix:///run/containerd/containerd.sock   0 }]  }"
module=grpc
time="2022-12-10T12:17:03.473573787-05:00" level=info msg="ClientConn
switching balancer to \"pick_first\"" module=grpc
time="2022-12-10T12:17:03.474530993-05:00" level=info msg="parsed scheme:
\"unix\"" module=grpc
time="2022-12-10T12:17:03.474545549-05:00" level=info msg="scheme \"unix\"
not registered, fallback to default scheme" module=grpc
time="2022-12-10T12:17:03.474563752-05:00" level=info
msg="ccResolverWrapper: sending update to cc:
{[{unix:///run/containerd/containerd.sock   0 }]  }"
module=grpc
time="2022-12-10T12:17:03.474571186-05:00" level=info msg="ClientConn
switching balancer to \"pick_first\"" module=grpc
time="2022-12-10T12:17:03.478908716-05:00" level=warning msg="Your kernel
does not support cgroup blkio weight"
time="2022-12-10T12:17:03.478927115-05:00" level=warning msg="Your kernel
does not support cgroup blkio weight_device"
time="2022-12-10T12:17:03.479037897-05:00" level=info msg="Loading
containers: start."
time="2022-12-10T12:17:03.495743563-05:00" level=info msg="failed to read
ipv6 net.ipv6.conf..accept_ra" bridge=docker0
syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
time="2022-12-10T12:17:03.518761943-05:00" level=info msg="Default bridge
(docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip
can be used to set a preferred IP address"
time="2022-12-10T12:17:03.518886881-05:00" level=info msg="failed to read
ipv6 net.ipv6.conf..accept_ra" bridge=docker0
syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
time="2022-12-10T12:17:03.534616741-05:00" level=info msg="Loading
containers: done."
time="2022-12-10T12:17:03.541080189-05:00" level=info msg="Docker daemon"
commit=a89b84221c graphdriver(s)=overlay2 version=20.10.17
time="2022-12-10T12:17:03.541122352-05:00" level=info msg="Daemon has
completed initialization"
time="2022-12-10T12:17:03.549888103-05:00" level=info msg="API listen on
/var/run/docker.sock"
time="2022-12-10T12:17:27.025622231-05:00" level=warning msg="Error getting
v2 registry: Get \"https://registry-1.docker.io/v2/\": net/http: request
canceled while waiting for connection (Client.Timeout exceeded while
awaiting headers)"
time="2022-12-10T12:17:27.025667054-05:00" level=info msg="Attempting next
endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\":
net/http: request canceled while waiting for connection (Client.Timeout
exceeded while awaiting headers)"
time="2022-12-10T12:17:27.026851821-05:00" level=error msg="Handler for
POST /v1.41/images/create returned error: Get \"
https://registry-1.docker.io/v2/\": net/http: request canceled while
waiting for connection (Client.Timeout exceeded while awaiting headers)"

time="2022-12-10T12:15:42.036053086-05:00" level=info msg="loading plugin
\"io.containerd.internal.v1.tracing\"..." type=io.containerd.internal.v1
time="2022-12-10T12:15:42.036068412-05:00" level=error msg="failed to
initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint:
skip plugin"
time="2022-12-10T12:15:42.036100189-05:00" level=info msg="loading plugin
\"io.containerd.grpc.v1.cri\"..." type=io.containerd.grpc.v1
time="2022-12-10T12:15:42.036390695-05:00" level=info msg="Start cri plugin
with config {PluginConfig:{ContainerdConfig:{Snapshotter:overlayfs
DefaultRuntimeName:runc DefaultRuntime:{Type: Path: Engine:
PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[]
PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir:
NetworkPluginMaxConfNum:0} UntrustedWorkloadRuntime:{Type: Path: Engine:
PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[]
PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir:
NetworkPluginMaxConfNum:0} Runtimes:map[runc:{Type:io.containerd.runc.v2
Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root:
Options:map[BinaryName: CriuImagePath: CriuPath: CriuWorkPath: IoGid:0
IoUid:0 NoNewKeyring:false NoPivotRoot:false Root: ShimCgroup:
SystemdCgroup:false] PrivilegedWithoutHostDevices:false BaseRuntimeSpec:
NetworkPluginConfDir: NetworkPluginMaxConfNum:0}] NoPivot:false
DisableSnapshotAnnotations:true DiscardUnpackedLayers:false
IgnoreRdtNotEnabledErrors:false}
CniConfig:{NetworkPluginBinDir:/opt/cni/bin
NetworkPluginConfDir:/etc/cni/net.d NetworkPluginMaxConfNum:1
NetworkPluginConfTemplate: 

Re: [gentoo-user] NAS and replacing with larger drives

[Michael]

On Saturday, 10 December 2022 16:30:03 GMT Wols Lists wrote:
> On 10/12/2022 16:19, Frank Steinmetzger wrote:
> > Where do we confuse those two? We specifically talked of codecs and
> > “contain”.
> 
> "I didn't know .ts could contain h264".
> 
> If .ts is the container, then surely the assumption is it can contain
> any codec? If not, why not?

Not any codec.  Some container formats are only compatible with certain 
codecs, or rather the other way around.  Have a look here:

https://en.wikipedia.org/wiki/Comparison_of_video_container_formats

I suppose the answer to 'why not' boils down to the whatever structure and 
data the container format is designed to be compatible with, but I don't know 
more than this.

https://en.wikipedia.org/wiki/File:Informatik-Containerformate-Beispiele.svg



signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] NAS and replacing with larger drives

[Wols Lists]

On 10/12/2022 16:19, Frank Steinmetzger wrote:

Where do we confuse those two? We specifically talked of codecs and
“contain”.


"I didn't know .ts could contain h264".

If .ts is the container, then surely the assumption is it can contain 
any codec? If not, why not?


(Yes I do get the impression I didn't read the OP properly. But then, 
the OP didn't make sense properly so I'm not surprised I got it wrong :-)


Cheers,
Wol

Re: [gentoo-user] NAS and replacing with larger drives

[Frank Steinmetzger]

Am Sat, Dec 10, 2022 at 09:20:17AM + schrieb Wols Lists:

> > > Depending on the PVR make/model I've seen 1080p resolution recordings with
> > > .m2ts and .ts file extensions, while the codecs inside them are the same.
-^^^
> 
> > I wasn’t aware that ts could contain h264. But then again—I never really
-^^^
> > bothered with live TV recordings in recent years.

> I think this is confusing CONTAINER and CODEC.

Where do we confuse those two? We specifically talked of codecs and
“contain”.

> .ts is a container format, h264 is a codec. I don't understand it myself,
> either but think of ts as your directory structure and h264 as your file
> structure.

Now you are confusing me. You say you don’t understand it, but then explain
it. TS is like AVI and MKV: a file structure for the payload data. And
payload data can be all kinds of stuff, from ASS plaintext subtitles, over
opus audio to mpeg2 or h264 video.

> Incidentally, sticking this stuff in a .tar is probably okay - that's just
> another container, but sticking it in a .tar.gz is not, the gz is your codec
> and will make the file BIGGER in all probability.

Tar does not compress, it simply puts all inputs in a 1:1 stream. It does
add some metadata (filename and so on). Packers reduce data volume by
increasing information-per-byte. So if the total information stays the same
(for lossless coding), the number of bytes decreases. Encoded video data
ideally has even entropy. It is indistinguishable from random noise. That’s
why compressing it again does not yield anything, or even adds some volume
again.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

“Mankind must put an end to war or war will put an end to mankind.”
 – John F. Kennedy


signature.asc
Description: PGP signature

Re: [gentoo-user] Duel boot - How to verify boot loader updates?

[Michael]

On Friday, 9 December 2022 18:39:33 GMT Mark Knecht wrote:
> On Fri, Dec 9, 2022 at 10:57 AM Michael  wrote:
> > On Friday, 9 December 2022 17:17:24 GMT Mark Knecht wrote:
> 
> 
> > > It's not totally a thought experiment. One machine I have which
> > > is dual boot recently complained that the original disk grub was
> > > installed on had changed when in fact there hadn't been any
> > > hardware changes and I had to carefully figure out how to
> > > answer a couple of questions. After the fact I started to wonder
> > > about this edge case.
> > > 
> > > I think it comes down to reading what's on the disk with a
> > > hex editor possibly but I know nothing about what to expect
> > > there.
> > > 
> > > Thanks,
> > > Mark
> > 
> > Before I venture a potentially wrong answer, could you please clarify if
> > we are talking about a UEFI MoBo, or a legacy BIOS MoBo.
> 
> The specific machine where this happened is UEFI.
> 
> Thanks

Without more information on the errors GRUB produced I can't comment on the 
specific experience you had, other than to say you can install GRUB on a 
different disk/partition than the one the OS is on.  Perhaps GRUB complained 
about being updated from a different OS used for its installation?

Anyway, let's briefly clarify the BIOS startup process you mentioned, if only 
to explain why I don't think this is related to the errors you mentioned.

On legacy boot systems the BIOS code is quite limited in what it can do.  It 
just jumps to the 1st disk, first sector (LBA 0) and runs what it finds there.  
This era of technology used the MBR disk partitioning scheme and the first 
sector contained the boot loader code as well as the disk partition table.

Modern UEFI systems use more capable EFI firmware (a.k.a. BIOS) and normally a 
GPT formatted disk.  This modern system does not require any boot loader code 
to be written in LBA 0.  The boot loader code is part of the UEFI firmware 
itself and is capable of loading and executing EFI compatible 'applications' 
stored in the FAT 32 formatted EFI/ partition (ESP) on the first disk.  GRUB's 
EFI executable 'grubx64.efi' stored in the ESP on the first disk is loaded and 
executed by the MoBo's UEFI firmware.

If I were to hazard a guess, the GRUB error messages you received are not 
related to the BIOS init sequence, but the GRUB configuration.  Probably some 
mismatch between the filesystem UUID, GRUB's root prefix and perhaps the 
PARTUUID between the current OS and the one used to clone/install GRUB in the 
OS at the beginning.  You could try to decipher this manually, by running 
blkid, to list your partitions and their respective UUID and PARTUUID.  Then 
editing grub.cfg and/or any files if necessary under /etc/default/

On the other hand, it would be easier to reinstall grub on the OS you are 
currently booted into, with 'grub-install' followed by 'grub-mkconfig' to 
update its grub.cfg file.  This should straighten out any discrepancies.


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] NAS and replacing with larger drives

[Wols Lists]

On 09/12/2022 13:38, Frank Steinmetzger wrote:

Depending on the PVR make/model I've seen 1080p resolution recordings with
.m2ts and .ts file extensions, while the codecs inside them are the same.



I wasn’t aware that ts could contain h264. But then again—I never really
bothered with live TV recordings in recent years. These days, if I find
something interesting, I download the show form the TV channel’s website
(called Mediathek in Germany, a word play on Bibliothek, meaning library).
Interestingly though, the picture quality is noticably worse than what I
receive via DVB-T.


I think this is confusing CONTAINER and CODEC.

.ts is a container format, h264 is a codec. I don't understand it 
myself, either, but think of ts as your directory structure and h264 as 
your file structure.


Incidentally, sticking this stuff in a .tar is probably okay - that's 
just another container, but sticking it in a .tar.gz is not, the gz is 
your codec and will make the file BIGGER in all probability.


Cheers,
Wol