buildah pull from registry.fedoraproject.org fails with error tls: unexpected message

[zerotri]

(Note: this is a different machine than the other issue I've posted, same install procedure)
I'm running a fresh Silverblue 29 install, rebased to 30 via these instructions: https://fedoramagazine.org/how-to-rebase-to-fedora-30-beta-on-silverblue/

A simple toolbox create fails:

[zerotri@weltall ~]$ toolbox -v create
toolbox: Fedora generational core is f30
toolbox: base image is fedora-toolbox:30
toolbox: customized user-specific image is fedora-toolbox-zerotri:30
toolbox: container is fedora-toolbox-zerotri:30
toolbox: checking value /var/run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: parsing value /var/run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: checking if image fedora-toolbox-zerotri:30 already exists
Error: error getting image "fedora-toolbox-zerotri:30": unable to find a name and tag match for fedora-toolbox-zerotri in repotags: no such image
toolbox: looking for image localhost/fedora-toolbox:30
Pulling docker://localhost/fedora-toolbox:30
ERRO[0000] exit status 1                                
toolbox: looking for image registry.fedoraproject.org/f30/fedora-toolbox:30
Pulling docker://registry.fedoraproject.org/f30/fedora-toolbox:30
ERRO[0000] exit status 1                                
toolbox: failed to pull base image fedora-toolbox:30

podman version 1.2.0

This is using the latest git revision of toolbox. Not sure how to proceed here.

[grdryn]

I also get this issue, and I've got a similar situation where I've recently rebased to Fedora Silverblue 30 from a recent Fedora Silverblue 29.

$ rpm -q podman
podman-1.2.0-2.git3bd528e.fc30.x86_64
$ rpm -q toolbox
toolbox-0.0.7-1.fc30.noarch

[debarshiray]

Yes, buildah pull on Fedora 30 is somehow unable to pull images from registry.fedoraproject.org. See containers/buildah#1504

[grdryn]

@debarshiray That issue seems to be fixed now (maybe it was a problem on the registry side? In any case, I'm now able to buildah pull registry.fedoraproject.org/f30/fedora-toolbox:latest, but I hit another issue:

toolbox -v create
toolbox: Fedora generational core is f30
toolbox: base image is fedora-toolbox:30
toolbox: customized user-specific image is fedora-toolbox-gryan:30
toolbox: container is fedora-toolbox-gryan:30
toolbox: checking if image fedora-toolbox-gryan:30 already exists
toolbox: checking if image fedora-toolbox-gryan:30 has volumes for host bind mounts
toolbox: checking if container fedora-toolbox-gryan:30 already exists
Error: error looking up container "fedora-toolbox-gryan:30": no container with name or ID fedora-toolbox-gryan:30 found: no such container
toolbox: trying to create container fedora-toolbox-gryan:30
Error: error running container create option: name must match regex [a-zA-Z0-9_-]+: invalid argument
toolbox: failed to create container fedora-toolbox-gryan:30

Thanks to the indicative error, I realised that I could name the container something else, so this works:

toolbox -v create --container test
toolbox: Fedora generational core is f30
toolbox: base image is fedora-toolbox:30
toolbox: customized user-specific image is fedora-toolbox-gryan:30
toolbox: container is test
toolbox: checking if image fedora-toolbox-gryan:30 already exists
toolbox: checking if image fedora-toolbox-gryan:30 has volumes for host bind mounts
toolbox: checking if container test already exists
Error: error looking up container "test": no container with name or ID test found: no such container
toolbox: trying to create container test
toolbox: created container test

[zerotri]

I feel like this was registry-side. I setup Silverblue on two systems nearly identically. The first got through the registry download phase and ran into the second issue you are seeing, #106 . About a day later, I go to setup toolbox having found the temporary workaround for the issue and I ran into this registry issue instead. That would hint at being registry side if the machines were setup identically.

[debarshiray]

@grdryn Yes, that's #106. Let's close this one now.

[alex285]

i just getting that
podman version 1.2.0
toolbox from master

./toolbox -v create

toolbox: resolved absolute path for ./toolbox to /var/home/me/Git/toolbox/toolbox
toolbox: TOOLBOX_PATH is /var/home/me/Git/toolbox/toolbox
toolbox: Fedora generational core is f30
toolbox: base image is fedora-toolbox:30
toolbox: customized user-specific image is fedora-toolbox-me:30
toolbox: container is fedora-toolbox-me-30
toolbox: checking value /var/run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: parsing value /var/run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: checking if image fedora-toolbox-me:30 already exists
toolbox: looking for image localhost/fedora-toolbox:30
Pulling docker://localhost/fedora-toolbox:30
ERRO[0000] exit status 1                                
toolbox: looking for image registry.fedoraproject.org/f30/fedora-toolbox:30
Pulling docker://registry.fedoraproject.org/f30/fedora-toolbox:30
ERRO[0000] exit status 1
toolbox: failed to pull base image fedora-toolbox:30                     

[alex285]

i have removed all containers and images, now if i do

buildah pull registry.fedoraproject.org/f30/fedora-toolbox:latest

i get:

Pulling docker://registry.fedoraproject.org/f30/fedora-toolbox:latest
1 error occurred:
	* Error determining manifest MIME type for docker://registry.fedoraproject.org/f30/fedora-toolbox:latest: pinging docker registry returned: Get https://registry.fedoraproject.org/v2/: local error: tls: unexpected message


ERRO[0000] exit status 1       

[debarshiray]

@alex285 what's your Buildah version (rpm -q buildah)? Could you please try with the buildah-1.7-18.git873f001.fc30 build?

The original issue with buildah pull failing with a TLS error on Fedora 30 has now been solved. Please feel free to open a separate issue if you are still encountering other problems.

If you have reason to believe that the TLS problem is still present, then please do leave a on containers/buildah#1504

[alex285]

hello @debarshiray
my Buildah was buildah-1.7-17.dev.git146a0fc.fc30.x86_64 and I'm running Silverblue, if that matters

i updated, and now I see a `buildah 1.7-17.dev.git146a0fc.fc30 -> 1.7-18.git873f001.fc30', but dont want to reboot right now. i will update the issue when i reboot!

[alex285]

ok, so tried now with Buildah 1.7-18.git873f001.fc30 and everything worked! it throws an ERROR and an EXIT 1 but it continues normally

./toolbox -v create

toolbox: resolved absolute path for ./toolbox to /var/home/me/Git/toolbox/toolbox
toolbox: TOOLBOX_PATH is /var/home/me/Git/toolbox/toolbox
toolbox: Fedora generational core is f30
toolbox: base image is fedora-toolbox:30
toolbox: customized user-specific image is fedora-toolbox-me:30
toolbox: container is fedora-toolbox-me-30
toolbox: checking value /var/run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: parsing value /var/run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: checking if image fedora-toolbox-me:30 already exists
toolbox: looking for image localhost/fedora-toolbox:30
ERRO[0000] exit status 1                                
Image required to create toolbox container.
Download registry.fedoraproject.org/f30/fedora-toolbox:30 (500MB)? [y/N]: y
toolbox: looking for image registry.fedoraproject.org/f30/fedora-toolbox:30
Getting image source signatures
Copying blob 934966bfd3bd [=================>--------------------] 42.8MiB / 89.2MiB
Copying blob 934966bfd3bd [======================================] 89.2MiB / 89.2MiB
Copying blob cd73137bf7d1 [======================================] 56.3MiB / 56.3MiB
Copying config dbfb7129d3 [======================================] 2.8KiB / 2.8KiB
Writing manifest to image destination
Storing signatures
toolbox: base image fedora-toolbox:30 resolved to registry.fedoraproject.org/f30/fedora-toolbox:30
toolbox: trying to create working container toolbox-working-container-4c393626-68e3-11e9-bc33-408d5c4d7835
toolbox: trying to configure working container toolbox-working-container-4c393626-68e3-11e9-bc33-408d5c4d7835
passwd: Note: deleting a password also unlocks the password.
passwd: Note: deleting a password also unlocks the password.
toolbox: trying to create image fedora-toolbox-me:30
Getting image source signatures
Copying blob 8dfabd2ae25c [======================================] 297.1MiB / 297.1MiB
Copying blob b892ac1dce6d [======================================] 160.6MiB / 160.6MiB
Copying blob 981e07209cac [======================================] 306.5KiB / 306.5KiB
Copying config c1fde7bd95 [======================================] 1.4KiB / 1.4KiB
Writing manifest to image destination
Storing signatures
toolbox: created image fedora-toolbox-me:30
toolbox: checking if image fedora-toolbox-me:30 has volumes for host bind mounts
toolbox: checking if container fedora-toolbox-me-30 already exists
toolbox: trying to create container fedora-toolbox-me-30
Created container: fedora-toolbox-me-30
Enter with: toolbox enter