Bug: Broken images from DockerHub makes Apx containers unusable

[sayber]

the APX package does not work =( Clean system, just installed

doc@vanilla:~$ apx init
⣾ Creating container...⌬ Apx :: error creating container: exit status 125

[rhcalderon]

I was just about to open an issue on this, as I'm getting the same error on a fresh install.

[phaon1]

also getting this issue too

[Andre-Capjoy]

same here, installed it twice in virtual box and both times I had this issue

[sayber]

Installed on two different laptops. The problem remains

[phaon1]

i was able to create a void sub system. still cant create others

[phaon1]

arch also worked. havent tested others yet but i know that the ubuntu sub system still gives exit code 125

[mirkobrombin]

Does it work using the apt flag?

[sayber]

@mirkobrombin "apk install" doesn't work for me, "apk install --apt*" doesn't work

[phaon1]

Does it work using the apt flag?

no it doesnt

[phaon1]

im not able to create a void sub system when using the flag but when i create one from the control center it works. ubuntu sub system doesnt work on either though

[kbdharun]

~~There is an issue with Ubuntu Registry Image~~. I had the same issue reported it in #dev.

[phaon1]

doesn't just affect ubuntu for me though, at least when using apx and not using the vanilla control center

[kbdharun]

doesn't just affect ubuntu for me though, at least when using apx and not using the vanilla control center

Oops, I forgot to edit the above comment, I wrote it this morning 😅 .

The issue occurs when a registry/docker image isn't pulled successfully. I had it with Ubuntu, but it could happen to any container too. Not sure what the cause of this issue is.

[phaon1]

ah, seems like a registry issue then, unfortunate

[mirkobrombin]

So just force re-pulling should make it works. I am not sure if we can automate this in Apx.

[kbdharun]

So just force re-pulling should make it works. I am not sure if we can automate this in Apx.

I will try and let you know if repulling the image works.

Update: Nope it doesn't work. Attaching the error image I shared in #dev in Discord. (We are investigating this in #dev)

[TheCorruptCat]

does not work for me ether

[nothing-fr]

I was able to make it work! I had to create ~/.config/containers/registries.conf with :

# Note that changing the order here may break tests.
unqualified-search-registries = ['docker.io', 'quay.io', 'registry.fedoraproject.org']

[[registry]]
# In Nov. 2020, Docker rate-limits image pulling.  To avoid hitting these
# limits while testing, always use the google mirror for qualified and
# unqualified `docker.io` images.
# Ref: https://cloud.google.com/container-registry/docs/pulling-cached-images
prefix="docker.io"
location="mirror.gcr.io"

# 2020-10-27 a number of images are not present in gcr.io, and podman
# barfs spectacularly when trying to fetch them. We've hand-copied
# those to quay, using skopeo copy --all ...
[[registry]]
prefix="docker.io/library"
location="quay.io/libpod"

(content from https://github.com/containers/podman/blob/main/test/registries.conf)

then apx init

On the long run, not sure if it's the right solution... (old images - ubuntu focal)

[phaon1]

ok i was able to create a void container using apx. i guess i was using the flags wrong as i was putting --xbps at the end of the command instead of apx --xbps install etc. ubuntu still wont work so i guess this actually might just be an issue with the ubuntu container

[nothing-fr]

I don't know why, but it seems to be working again without modifications... strange... maybe a fix on the docker registry side...

[phaon1]

I don't know why, but it seems to be working again without modifications... strange... maybe a fix on the docker registry side...

yep its working again for me

[jardon]

This issue appears to no longer be an issue as of apx version 2. If the issue persists in the latest build, please feel free to reopen this issue.