Well, the URL on master definitely works if you use “docker build https://github.com/daos-stack/daos.git#master -f utils/docker/Dockerfile.centos.7” Johann From:<daos@daos.groups.io> on

Ok, I’ve reproduced this. The issue is the dockerfile in 1.0.1 is doing a git clone rather than a COPY to get the code, so the dockerfile is fetching the wrong data. I guess the fix would be to

Hi, Sorry for the confusion. The structure of the docker files was modified some time ago and we updated the documentation (in the source code too) accordingly, but the online github I/O pages

Hi Ashley, I ran the following 3 commands: git clone --recurse-submodules -b v1.0.1 https://github.com/daos-stack/daos.git cd daos docker build

It looks like you’re trying to use 1.0.1? I’ve just checked that out locally and there’s no reference to patchelf at all in the source tree at that point, we use it now for checking that build

Hi Ashley, Thank you so much for the response. I was in the wrong directory it seems. Although when I try now, the build stops with the following error :- [...] at include/opa_user.h

Hi Johann, I ran the exact same command: docker build https://github.com/daos-stack/daos.git#master:utils/docker \ -f Dockerfile.centos.7 -t daos My major use case of connecting my Python API with the

For testing purpose, I run the servers and agents in the foreground. I press ctrl-c to stop servers and agents. Then, I start the servers one after the other and restart all agents on servers and

Hi Mohamad, On the client node, I stopped the old agent and restart agent again. Ping

Hi Ping, Did you restart the agent on the client side or did you have an older agent running? Thanks, Mohamad From:daos@daos.groups.io <daos@daos.groups.io> on behalf of ping.wong via

Hi Johann, Since I ran both servers as root, I did umount /mnt/root and rm -rf /mnt/root before restarting both servers and agents. I am using Then I did the storage format. After format, I restart

Hey Ping, I did look into your logs and notice messages like “Could not lookup ofi+sockets://11.11.200.48:31416” which mean that sockets URIs (instead of tcp) are still registered and storage

Hi Johann, I did reformat and restart all agents on client node and the two servers. Both servers using ofi+tcp;ofi_rxm provider start fine; however, the client application failed. Please refer the

I was trying to setup DAOS from scratch following the documentation. I am doing it from scratch because I have a ubuntu machine and can not use the RPM built. Also, I want to understand the project

This will create a build a docker image using the Dockerfile from github, but the sources from the current directory so you need to do this from a checked-out copy of the source tree. Ashley.

Hi, Could you please advise what docker command you ran? “docker build https://github.com/daos-stack/daos.git#master:utils/docker -f Dockerfile.centos.7” should work fine. Regarding the

Hi Ping, Sorry, I should have provided more details in my previous email. After switching toofi+tcp;ofi_rxm in the config file, you will have to reformat and restart the agent since we don’t

I am trying to Set-up the DAOS system on my local machine. So, when I am trying to run the DockerFile for the same, it gives me the following error: Also, I want to connect my REST API to the DAOS

Hi Johann, I have the control interface on 10Gbps Ethernet and the data plane interface is on 100Gbps Ethernet. Per your recommendation, I tried ofi+tcp;ofi_rxm; however, the client application

One roundtrip from client to leader and then one from leader to each other replica (i.e. one roundtrip for 2-way replication since the leader is a replica). Please check Liang’s paper