Hi Nigel,

 

You are correct on the tags in Atlas git repo:

    - Atlas 2.2.0 release: 2.2.0-rc1

    - Atlas 2.3.0 release: 2.3.0-rc1 (to be released shortly)

 

About building and running Atlas in docker containers, 
dev-support/atlas-docker/README.md has the most recent instructions.

 

> failed to solve: rpc error: code = Unknown desc = failed to solve with 
> frontend dockerfile.v0: failed to create LLB definition: pull access denied, 
> repository does not exist or may require authorization: server message: 
> insufficient_scope: authorization failed
It has been a while since I built atlas-base and atlas-build docker images; 
hence I haven’t seen above error you encountered. However, I encountered this 
issue in a new machine. As you suggested, after building atlas-base image 
separately, build of Atlas using docker went through successfully.

 

> atlas-build  | [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on 
> project atlas-buildtools: Failed to clean project: Failed to delete 
> /home/atlas/src/build-tools/target/classes/checkstyle-suppressions.xml -> 
> [Help 1]
Can you please verify if /home/atlas/src is writable from Docker? This is a 
link to Atlas source root directory i.e. ../.. from dev-support/atlas-docker 
directory. You can find details in docker-compose.atlas-build.yml.

 

Hope this helps.

 

Madhan

 

From: Nigel L Jones <[email protected]>
Reply-To: <[email protected]>
Date: Tuesday, December 6, 2022 at 1:47 PM
To: "[email protected]" <[email protected]>
Subject: Running Atlas - in docker

 

Hi,
I’m looking at running Atlas (just for a demo/test, not prod). Ideally k8s 
(especially helm chart), but otherwise docker/compose.

I note we have more content for docker-compose under dev-support that when I 
last looked, but had a few questions

* As of today the latest tags are
- release-2.3.0-rc1

- release 2.2.0-rc1

Are these effectively the 2.2.0 & 2.3.0 releases? 

In dev-support there’s a readme that gets the user to
     ./download-archives.sh

        docker-compose -f docker-compose.atlas-base.yml -f 
docker-compose.atlas-build.yml up

 

I noticed this second command fails without an ‘atlas-base’ image built:

➜  atlas-docker git:(master) docker-compose -f docker-compose.atlas-base.yml -f 
docker-compose.atlas-build.yml up

[+] Running 0/2

⠿ atlas-build Warning                                                           
                                                                                
                   1.0s

⠿ atlas-base Warning                                                            
                                                                                
                   1.0s

[+] Building 0.8s (8/8) FINISHED

=> [atlas-base internal] load build definition from Dockerfile.atlas-base       
                                                                                
                   0.0s

=> => transferring dockerfile: 1.82kB                                           
                                                                                
                   0.0s

=> [atlas-build internal] load build definition from Dockerfile.atlas-build     
                                                                                
                   0.0s

=> => transferring dockerfile: 1.51kB                                           
                                                                                
                   0.0s

=> [atlas-base internal] load .dockerignore                                     
                                                                                
                   0.0s

=> => transferring context: 227B                                                
                                                                                
                   0.0s

=> [atlas-build internal] load .dockerignore                                    
                                                                                
                   0.0s

=> => transferring context: 227B                                                
                                                                                
                   0.0s

=> CANCELED [atlas-base internal] load metadata for 
docker.io/library/ubuntu:20.04                                                  
                                               0.7s

=> ERROR [atlas-build internal] load metadata for 
docker.io/library/atlas-base:latest                                             
                                                 0.6s

=> [auth] library/ubuntu:pull token for registry-1.docker.io                    
                                                                                
                   0.0s

=> [auth] library/atlas-base:pull token for registry-1.docker.io                
                                                                                
                   0.0s

------

> [atlas-build internal] load metadata for docker.io/library/atlas-base:latest:

------

failed to solve: rpc error: code = Unknown desc = failed to solve with frontend 
dockerfile.v0: failed to create LLB definition: pull access denied, repository 
does not exist or may require authorization: server message: 
insufficient_scope: authorization failed

So I decided to build the docker image with:

docker build -f Dockerfile.atlas-base -t atlas-base:latest .

This build ok, and the previous compose command then ran until it failed later 
with:

atlas-build  | [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on 
project atlas-buildtools: Failed to clean project: Failed to delete 
/home/atlas/src/build-tools/target/classes/checkstyle-suppressions.xml -> [Help 
1]

I noticed some references in the latest emails indicating some docker 
improvements, so could someone point me in the right direction to get things 
working. I can probably figure it out from the docker and compose files, but 
was thinking it should pretty much ‘just work’ from the sources provided? 

Are there additional things required – images in a container registry? Manual 
building of any of the other Dockerfiles? Additional maven repos? 

Thanks
Nigel.

 

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Reply via email to