Closed iKK001 closed 1 year ago
Should be fixed, closing in favour of: https://forums.balena.io/t/xserver-image-pull-access-denied/366366
excellent, now it works ! Thank you very much.
I can now add the following inside my docker-compose.yml file and it compiles...
xserver:
image: bh.cr/balenalabs/xserver-amd64
I tried to change the xserver service in my Balena project from
balenablocks
tobalenalabs
.Is it correct that
balenalabs
is newer thanbalenablocks
? Or which one do you recommend ?The following error occurs when trying to go from
balenablocks
tobalenalabs
version of xserver:Before, I had the following inside the
docker-compose.yml
File:For the above, everything works and I can push to the Balena fleet without problems.
However, if I exchange the
balenablocks/xserver
withbh.cr/balenalabs/xserver-amd64
, such as:Then I get the following error message when trying to push to the balena fleet :
I also tried
image: bh.cr/balenalabs/xserver
(i.e. without the-amd64
). But did not help, same error !!!Then I tried to upload my own custom Balena Block from a cloned xserver instance. It did it. It worked and under Balena Blocks I find my own custom Block:
Inside the
docker-compose.yml
File, I exchanged to now take my custom Block, such as:or also:
It did not work !!!!!!!
Again, when trying to push my project to the fleet, I end up once more with the exact same error message:
What do I need to do ?
Which of the two xserver possibilities do you recommend ? (i.e. balenablocks/xserver or balenalabs/xserver ??)