infinit / infinit Goto Github PK
View Code? Open in Web Editor NEWThe Infinit policy-based software-defined storage platform.
Home Page: http://infinit.sh
The Infinit policy-based software-defined storage platform.
Home Page: http://infinit.sh
Hello all!
I've followed the Getting Started guide (a lot of the commands syntax were deprecated, as mentioned on another issues), but could not continue with the installation of the docker plugin as it needs to be ran as root. As I've created users in the Getting Started guide, these were saved under the other users' path (/home/non-root-user/.local/share/infinit/filesystem/users/...
), so the sudo /opt/infinit/bin/infinit daemon run --as my-infinit-user --docker-user non-root-user
(found in Docker Volume) yields:
/opt/infinit/bin/infinit: fatal error: user "my-infinit-user" does not exist
What can I do in these cases? Create a home for my root user and copy the contents of /home/non-root-user/.local/share/infinit
?
Cheers,
Pedro
Dear Guru's,
I have a plan to run a hyper-convergent with CoreOS on digitalocean. In order to to that, these are the steps I take to create an infinit volume to be used by my containers.
docker run --rm --privileged -v /home/core/infinit:/root -v /run:/run -v /etc/docker/plugins:/var/lib/docker/plugins -it infinit/infinit bash
infinit user create --name username --fullname 'User Name'
infinit silo create filesystem --name local
infinit network create --as username --name cluster --storage local
infinit volume create --as username --network cluster --name shared
infinit volume mount --as username --name shared --mountpoint ~/mnt --allow-root-creation &
echo 'Hello world' > ~/mnt/hello.txt
cat ~/mnt/hello.txt
Everything is working great up to this point. I can even stop and remove the container and later recreate the container with
docker run --rm --privileged -v /home/core/infinit:/root -v /run:/run -v /etc/docker/plugins:/var/lib/docker/plugins -it infinit/infinit bash
infinit volume mount --as username --name shared --mountpoint ~/mnt --allow-root-creation &
cat ~/mnt/hello.txt
and the data is still there. This is expected as infinit's data is persisted at host.
Okay, next this is what I do to create a volume for other container with the container volume plugin (daemon).
docker run --rm --privileged -v /home/core/infinit:/root -v /run:/run -v /etc/docker/plugins:/var/lib/docker/plugins -it infinit/infinit bash
infinit daemon start --as username
After this the appropriate docker plugin files should be in place on the host because of the host binding at /run
and /etc/docker/plugins
. When you check with docker volume ls
, the volume is listed, cool.
Then I proceed to create a new container to use the volume with
docker run --rm -v username/shared:/infinit -it alpine ash
I can access the directory fine and even create file and read it back. Everything seems fine without error until I notice that the file I created inside the volume, hello.txt
, is missing from this mounted volume.
When I destroy this alpine container and create another one, all the data created previously in the last alpine container is gone yielding yet another empty /infinit
.
But if I were to leave the first alpine container running, data created on the first alpine is there for the second alpine container and everything seems to works fine with the volume on both of those container except for the file hello.txt
which is still missing. And this works fine until all the container mounting the volume is destroy. The next time a new container mount the volume, and everything start empty again.
The infinit version inside the container is 0.8.0.
I have continuously take features such as hub, cache, docker swarm out of the equation.
Can any of the guru's here help me with this? Do let me know if you need any other extra information.
I infinit v0.7.3, the command for creating a new silo is:
# infinit silo create --filesystem --capacity 2GB --name local
But in v0.8.0, the same command says:
# infinit silo create --filesystem --capacity 2GB --name local
infinit: command line error: unknown option: --filesystem
Try 'infinit create --help' for more information.
The problem is solved by using
infinit silo create filesystem --capacity 2GB --name local
There is no information about this in documentation, so u guess it is either bug in silo binary, or in docs.
Hi ,
I have 3 ubuntu server (16.10) with docker 1.13 and docker-compose 1.8 .
I run swarm on top of the server .
I'm using docker-compose version '3'.
File format version: '3' networks: test: external: true volumes: test-user/test-volume: driver: infinit services: webapps: image: xxxxxxxxxxx networks: - test ports: - "80:8080" - "443:8443" volumes: - test-user/test-volume:/var/lib/jetty/webapps - test-user/test-volume::/var/lib/jetty/etc - test-user/test-volume::/var/lib/jetty/agents When I run
sudo docker stack deploy -c docker-compose-stack.yml test`
I get the error
test-user/test-volume Additional property test-user/test-volume is not allowed.
Also tried to run docker run -it --rm --volume-driver infinit -v test/test-volume:/path/to/mount alpine ash
I get the same error .
Best Regards
Following the Get Started guide, after creating a local storage, I tried both:
infinit network create --as my-username --storage local --name my-local-storage --push
and
infinit-network --create --as my-username --storage local --name my-local-storage --push
But it always returns:
infinit-network: fatal error: json parse error
Details:
Ubuntu 16.04.2 64bit
Linux Kernel 4.8.0-36-generic
Infinit 0.7.3
Hi - I have a question about running a infinit volume plugin inside docker container. Guys from docker says it should be doable with no problems.
I followed manual, except I ran the daemon in container. So my steps were:
docker run -it --name infinit-volume-plugin -v /var/run/docker.sock:/var/run/docker.sock --network infinit-network --privileged mefyl/infinit bash
docker version
)infinit daemon run --docker-user root
docker volume ls
Pretty much the same steps worked on host itself... Any ideas?
Also I found out the new "docker plugin" concept. Is infinit going to create this kind of volume plugin?
(First of all, congratulations to the project)
Description:
After correctly installing infinit
package in Ubuntu 16.04 64bit, I installed infinit-desktop
and tried to create an account.
The following message is returned:
It seems that infinit-desktop
is using an old command syntax.
Steps to reproduce:
Choose a computer (or VM) with Ubuntu 16.04 64bit
Install infinit
package according to official instructions ( https://infinit.sh/download )
Install infinit-desktop
package according to official instructions ( https://infinit.sh/drive )
Run the binary /opt/infinit-desktop/bin/infinit
and try to create an account
Details:
Ubuntu 16.04 64bit
Infinit 0.7.3
Infinit-Desktop 0.3.0
Edit
The problem persist even after correctly adding /opt/infinit/bin
to PATH
Trying to purge user from hub fails with:
infinit user delete --as dominik1 --name dominik1 --pull --purge
WARNING: The local copy of the user's private key will be removed.
WARNING: You will no longer be able to perform actions on https://beyond.infinit.sh
WARNING: for this user.
Confirm the name of the user you would like to delete: dominik1
[infinit] [main] HTTP response: <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.10.0 (Ubuntu)</center>
</body>
</html>
infinit: fatal error: unexpected HTTP error Bad Gateway deleting user "dominik1"
infinit version: 0.8.0
Creating a new user fails:
/opt/infinit/bin/infinit user create --name iojdji322s --push-user
Generating RSA keypair.
Locally saved identity for user "iojdji322s".
/opt/infinit/bin/infinit: fatal error: unexpected HTTP error Bad Gateway pushing user:
Unknown error
apt-cache policy infinit
infinit:
Installed: 0.8.0
Candidate: 0.8.0
This infinit user create worked a few days ago on the same machine. It also fails on a newly intalled VM. This is similar to issue #24 (which is closed now).
I don't know how to reproduce this situation, but my entire infinite volume, on all devices in the network, stopped accepting writes today.
From the error log I found the following assertion error:
[ elle.assert ] [fuse loop] assertion 'start_block == end_block - 1' failed at /builds/infinit/memo/src/infinit/filesystem/FileHandle.cc:385
[ elle.assert ] [fuse loop] #0 0x000000007fffffff: elle::AssertError::AssertError(char const*, char const*, unsigned long) +0x571
#1 0x000000007fffffff: elle::_abort(std::string const&, char const*, int) +0xa7
#2 0x000000007fffffff: infinit::filesystem::FileBuffer::_write_multi_multi(infinit::filesystem::FileHandle*, elle::ConstWeakBuffer, long, int, int) +0x125
#3 0x000000007fffffff: infinit::filesystem::FileBuffer::write(infinit::filesystem::FileHandle*, elle::ConstWeakBuffer, unsigned long, long) +0x29f
#4 0x000000007fffffff: infinit::filesystem::FileHandle::write(elle::ConstWeakBuffer, unsigned long, long) +0x2c
#5 0x000000007fffffff: ???
#6 0x000000007fffffff: fuse_fs_write_buf +0x230
#7 0x000000007fffffff: ???
#8 0x000000007fffffff: ???
#9 0x000000007fffffff: ???
#10 0x000000007fffffff: __fuse_process_cmd +0x17
#11 0x000000007fffffff: elle::reactor::FuseContext::_loop_single() +0x1c3
#12 0x000000007fffffff: elle::reactor::Thread::_action_wrapper(std::function<void ()> const&) +0x249
#13 0x000000007fffffff: ???
#14 0x000000007fffffff: make_fcontext +0x21
terminate called after throwing an instance of 'elle::AssertError'
what(): assertion 'start_block == end_block - 1' failed at /builds/infinit/memo/src/infinit/filesystem/FileHandle.cc:385
The version is
$ infinit --version
0.8.0
Thanks,
Tony
Reproduce:
Windows Machine with 0.8.0
Create user and push to beyond (user segatorpc)
create network and push to beyond (network segatorpc/net)
Transmit User
linux Machine with 0.8.0
Receive user (receive user segatorpc)
Fetch Network (fetch network net)
infinit network fetch --as segatorpc --name segatorpc/net
or
infinit network fetch --as segatorpc --name net
Locally fetched network descriptor "segatorpc/net".
infinit: fatal error: invalid type for key "", expected a long got a std::__cxx11::basic_string<char, std::char_traits, std::allocator >
/infinit network create --as clinfinit --silo local --replication-factor 3 --name cluster --push
Locally linked network descriptor "clinfinit/cluster".
Locally saved network descriptor "clinfinit/cluster".
./infinit: fatal error: unexpected HTTP error Bad Gateway pushing network:
Unknown error
I have setup up inifnit 0.7.3 on Ubunut Xenial on two machines on EC2.
I' have created user, network and volumes in one machine and mounted it.
Now when I'm trying to access infinit volume from another machine getting below execption
infinit volume mount --as rajivr --name rajivr/my-volume --mountpoint /root/mnt-rajiv-volume --allow-root-creation --cache --publish
Running network "rajivr/my-network".
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x24b0570): compatibility version 0.7.3
Running volume "rajivr/my-volume".
[infinit.model.doughnut.Dock] [rdv_connect] Dock RDV connect: execption network operation timed out
[infinit.model.doughnut.Dock] [rdv_connect] Dock RDV connect: execption network operation timed out
[infinit.model.doughnut.Dock] [rdv_connect] Dock RDV connect: execption network operation timed out
I have followed Getting Started Guide by replacing the depricated commands.
Hi,
I created two node configuration, and silo that is replicated on both of them.
I tested HA features and di thing like that:
"/mnt/Buba"[ infinit.filesystem.Unknown ] [fuse loop] File Buba exists where it should not [ infinit.filesystem ] [fuse loop] data not found fetching 0x895dda8f00("/Buba"): missing block: 0x895dda8f5a7b1262ea31c2d739af259490f0e6f6989b31f2dd4c15bae5875100
ls mount folder shows only files previuosly created before experiment, but file Buba.
Creating file without any content also raise same error:
sudo touch /mnt/Buba [ infinit.filesystem.Unknown ] [fuse loop] File Buba exists where it should not [ infinit.filesystem ] [fuse loop] data not found fetching 0x895dda8f00("/Buba"): missing block: 0x895dda8f5a7b1262ea31c2d739af259490f0e6f6989b31f2dd4c15bae5875100
My test stack:
I if you PM me I can give you full access to both machines, couse they are only test machines, no usefull data.
I'm trying to setup Docker Volume plugin by following the guide https://infinit.sh/documentation/docker/volume-plugin
Here's the commands I have used
docker run -it --rm --volume-driver infinit -v rajivr/my-volume:/mnt ubuntu:trusty /bin/bash
Docker volume looks fine
docker volume ls
DRIVER VOLUME NAME
infinit rajivr/my-volume
But the deprecated command infinit-volume is getting executed from docker
ps -ef | grep volume
root 17467 17461 0 10:14 ? 00:00:13 /opt/infinit/bin/infinit-volume --run rajivr/my-volume --as rajivr --fuse-option allow_root --push --mountpoint /run/user/0/infinit/filesystem/mnt/rajivr_my-volume-f764-79e5-43d1-a83c
Any fix for this issue?
Running infinit in a container whose user id is modified with docker-run's option --user
leads to the following error:
[elle.assert] [main] assertion 'could not determine username' failed at /builds/infinit/memo/elle/src/elle/system/username.cc:36
[elle.assert] [main] #0 0x000000007fffffff: elle::AssertError::AssertError(char const*, char const*, unsigned long) +0x507
#1 0x000000007fffffff: elle::_abort(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*, int) +0xc2
#2 0x000000007fffffff: elle::system::username[abi:cxx11]() +0x246
I simply wanted to avoid the usual permission problems of files created inside a container accessed from the host (for example to create a backup).
It's easy to reproduce:
$ docker run --name infinit --detach --interactive --privileged --restart=always --user (id -u):(id -g) --volume $HOME:$HOME --workdir $HOME --env INFINIT_HOME=$HOME infinit/infinit bash
$ docker exec -it infinit bash
I have no name!@f65ef37df35c:/Users/julio$ env
HOSTNAME=f65ef37df35c
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/Users/julio
SHLVL=1
HOME=/
no_proxy=*.local, 169.254/16
INFINIT_HOME=/Users/julio
_=/usr/bin/env
I have no name!@f65ef37df35c:/Users/julio$ infinit doctor all
[elle.assert] [main] assertion 'could not determine username' failed at /builds/infinit/memo/elle/src/elle/system/username.cc:36
[elle.assert] [main] #0 0x000000007fffffff: elle::AssertError::AssertError(char const*, char const*, unsigned long) +0x507
#1 0x000000007fffffff: elle::_abort(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*, int) +0xc2
#2 0x000000007fffffff: elle::system::username[abi:cxx11]() +0x246
#3 0x00000000005bcd18: ???
#4 0x00000000004f2857: ???
#5 0x00000000005c0c56: ???
#6 0x00000000005c2379: ???
#7 0x00000000005c3142: ???
#8 0x000000007fffffff: elle::reactor::Thread::_action_wrapper(std::function<void ()> const&) +0x259
#9 0x000000007fffffff: ???
#10 0x000000007fffffff: make_fcontext +0x21
terminate called after throwing an instance of 'elle::AssertError'
what(): assertion 'could not determine username' failed at /builds/infinit/memo/elle/src/elle/system/username.cc:36
Aborted
I have no name!@f65ef37df35c:/Users/julio$ infinit --help
[elle.assert] [main] assertion 'could not determine username' failed at /builds/infinit/memo/elle/src/elle/system/username.cc:36
[elle.assert] [main] #0 0x000000007fffffff: elle::AssertError::AssertError(char const*, char const*, unsigned long) +0x507
#1 0x000000007fffffff: elle::_abort(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*, int) +0xc2
#2 0x000000007fffffff: elle::system::username[abi:cxx11]() +0x246
#3 0x00000000005bcd18: ???
#4 0x00000000004f2857: ???
#5 0x00000000005c0c56: ???
#6 0x00000000005c2379: ???
#7 0x00000000005c3142: ???
#8 0x000000007fffffff: elle::reactor::Thread::_action_wrapper(std::function<void ()> const&) +0x259
#9 0x000000007fffffff: ???
#10 0x000000007fffffff: make_fcontext +0x21
terminate called after throwing an instance of 'elle::AssertError'
what(): assertion 'could not determine username' failed at /builds/infinit/memo/elle/src/elle/system/username.cc:36
Aborted
I have no name!@f65ef37df35c:/Users/julio$
Defining the variable INFINIT_USER
to try to avoid the error has no effects.
Built infinit into a docker image (because host is CentOS and binary does not run - incompatible link library version) - fuse
is installed on host and user_allow_other
is enabled.
I run the container: docker run -it --rm --privileged -v named_volume:/root/.local local/infinit
and inside it:
# username already created beforehand
infinit user login --name username
infinit silo create --filesystem --name local --capacity 50GB
infinit network create --as username --silo local --name main --push
volume create --as username--network main --name main --push
I then exit the container and recreate it with:
docker run -it --rm --privileged \
-v named_volume:/root/.local -v /opt/infinit:/inf local/infinit \
infinit volume mount --as username --name main --mountpoint /inf \
--allow-root-creation --cache --publish
Output:
Running network "username/main".
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x2b6c9f0): compatibility version 0.7.3
Running volume "username/main".
Then (on another terminal) I exec into the container to test if it works:
docker exec -it ID bash
and inside cd /inf; ls
Output in the first terminal now shows:
[infinit.filesystem ] [fuse loop] unexpected exception storing 0xd2c04428706a513ea3324748717d181ffeb904d36cfc3f25b82b071d9ccee900: no peer available for insertion of 0xd2c0442800
[infinit.filesystem ] [fuse loop] unexpected exception storing 0xf0cf726b6c82d7f6a6b741af4816f5e560647b151565ca6e11b1f52c80a6c100: no peer available for insertion of 0xf0cf726b00
[infinit.filesystem ] [fuse loop] unexpected exception storing 0x240809fa8a80753fe81300209929f73aa6f47bc8d9b02332f2e1226e306a4100: no peer available for insertion of 0x240809fa00
Am I missing something or is is a bug?
i found the changelog is release v0.8.1, but the install page, i found the release tar is v0.8.0, could you please use some CI system to build the tar automatly.
Following: https://infinit.sh/get-started
root@e8ae86e921e6:/# infinit --version
0.7.3
root@e8ae86e921e6:/# infinit user list
root@e8ae86e921e6:/# infinit user hash alice
infinit: fatal error: user "alice" does not exist
root@e8ae86e921e6:/# infinit user signup --name alice
Generating RSA keypair.
infinit: fatal error: user "alice" already exists with a different key
I want to deploy 200 stateful containers (databases) with Docker and use Infinit to store it's data. And also I'm going to use a clustered Minio deployment as S3 compatible storage driver for Infinit. But I think my databases will be slow. Am I right?
Examples:
1.
$ infinit volume create --as fankserver --name test --network cluster --fetch --push --create-root
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0xe06830): compatibility version 0.7.3
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on tcp://[::]:51671
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on utp://[::]:51671
[ cli.volume ] [main] create root directory
Locally saved volume descriptor "fankserver/test".
infinit: ../nptl/pthread_mutex_lock.c:350: __pthread_mutex_lock_full: Assertion `(-(e)) != 3 || !robust' failed.
Aborted
$ infinit volume create --as fankserver --name test2 --network cluster --fetch --push --create-root
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x1598830): compatibility version 0.7.3
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on tcp://[::]:40028
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on utp://[::]:40028
[ cli.volume ] [main] create root directory
Locally saved volume descriptor "fankserver/test2".
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
Aborted
2.1 Tried command again
$ infinit volume create --as fankserver --name test2 --network cluster --fetch --push --create-root
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x1d43830): compatibility version 0.7.3
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on tcp://[::]:35855
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on utp://[::]:35855
[ cli.volume ] [main] create root directory
Segmentation fault
$ infinit volume create --as fankserver --name test3 --network cluster --fetch --push --create-root
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x1de7830): compatibility version 0.7.3
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on tcp://[::]:52573
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on utp://[::]:52573
[ cli.volume ] [main] create root directory
Locally saved volume descriptor "fankserver/test3".
Segmentation fault
infinit volume create --as fankserver --name test4 --network cluster --fetch --push --create-root
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x13e5830): compatibility version 0.7.3
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on tcp://[::]:53805
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on utp://[::]:53805
[ cli.volume ] [main] create root directory
Locally saved volume descriptor "fankserver/test4".
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
Aborted
List volumes:
$ infinit volume list --as fankserver
fankserver/test4: network fankserver/cluster
fankserver/test2: network fankserver/cluster
fankserver/test: network fankserver/cluster
fankserver/test3: network fankserver/cluster
I went through the getting started documentation, both on macOS and linux. I end up with the same problem on both: unusable for write-intensive operations.
I reduced the case to a subset of the "get started" doc: one user, one volume, one network (replication = 2), one silo, and everything locally:
I then use any write-intensive program. My favorite simple stress test is using Keynote on a packaged presentation (i.e. it's a package of files instead of a single monolithic one) which modifies a lot of files as soon as you move a single byte in the presentation. In my case, editing a keynote presentation stored in a volume is almost impossible since. Same thing on linux untaring gcc sources (10 minutes for 1.8 GiB) or compiling then (stopped before the end). It's always ~3 MiB/second.
I can provide detailed logs if required.
Hello, trying to give infinit a spin and running into the following. I am new hear, any guidance appreciated. I saw a closed bug similar to this for 'alice' user not having a unique name. I tried 'ron', now 'ronabc'.
root@92a9d70a199d:/# infinit user signup --name ronabc --fullname "Ronabc"
Generating RSA keypair.
Remotely created identity for user "ronabc".
Locally saved identity for user "ronabc".
root@92a9d70a199d:/# infinit network create -as ronabc --storage local --name my-network --push
infinit: fatal error: user "root" does not exist
root@92a9d70a199d:/#
:-)
Hello to everyone in Infinit team and all community!
I would like your opinion on Raft algorithm (sources and implementations) as a better alternative to Paxos.
Their research, "In Search of an Understandable Consensus Algorithm," seems to me very interesting, and I believe using it can make Infinit more resilient and with a better fault tolerance.
Hi,
I followed the steps as listed here, for Debian, as I am on Ubuntu 16.04 LTS.
All the steps complete normally, until I mount 2 volumes. For each individual command, Infinit gives me this notice:
[infinit.model.doughnut.Doughnut] [main] Not using UTP although network configuration selects 'all' protocols. UTP has been temporarily deprecated. Force with INFINIT_UTP=1.
[ infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7f7ee487b410): creation failed, metrics will not be exposed: null context when constructing CivetServer. Possible problem binding to port.
Additionally I get this notice upon mounting the 2nd volume:
[ infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7f7ee487b410): creation failed, metrics will not be exposed: null context when constructing CivetServer. Possible problem binding to port.
What should I do to prevent or fix this?
Thank you,
Alex
$ infinit credentials list
Google Drive:
__my_email__: Simone Esposito
$ infinit silo create google-drive --account __my_email__ -c 100TiB --name gdrive
Locally saved silo "gdrive".
$ infinit network create --storage gdrive--name my-network-2 --push
Locally linked network descriptor "chauffer/my-network-2".
Locally saved network descriptor "chauffer/my-network-2".
Remotely already updated network descriptor "chauffer/my-network-2".
$ infinit doctor configuration
[OK] User
[OK] Silos
[ERROR] Networks:
[ERROR] chauffer/my-network-2 is faulty because "gdrive" (missing) silo is faulty
[OK] Volumes
[OK] Drives
[OK] Leftovers
infinit: fatal error: Please refer to each individual error message. If you cannot figure out how to fix your issues, please visit https://infinit.sh/faq.
If I try to create a volume:
$ infinit volume create --network my-network-2 --name my-volume-2 --push
Locally saved volume descriptor "chauffer/my-volume-2".
Remotely created volume descriptor "chauffer/my-volume-2".
$ infinit doctor configuration
[OK] User
[OK] Silos
[ERROR] Networks:
[ERROR] chauffer/my-network-2 is faulty because "gdrive" (missing) silo is faulty
[ERROR] Volumes:
[ERROR] chauffer/my-volume-2 is faulty because network "chauffer/my-network-2" is faulty
[OK] Drives
[OK] Leftovers
infinit: fatal error: Please refer to each individual error message. If you cannot figure out how to fix your issues, please visit https://infinit.sh/faq.
If I try mounting it:
infinit volume mount --as chauffer --name my-volume-2 --mountpoint ~/first-volume --allow-root-creation --cache --publish -v
Running network "chauffer/my-network-2".
[infinit.Network] [main] client version: 0.8.0
[infinit.model.Model] [main] infinit::model::Model(0x7fa06180ec00): compatibility version 0.8.0
[infinit.model.doughnut.Doughnut] [main] Not using UTP although network configuration selects 'all' protocols. UTP has been temporarily deprecated. Force with INFINIT_UTP=1.
[ infinit.model.doughnut.Local ] [main] dht::Local(0x7fa06100a720, 0x0f476e5d00): listen on tcp://[::]:59647
[ infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x102e86a50): listen on 127.0.0.1:8080
infinit: fatal error: Not implemented yet.
infinit volume push --name shared --as sensored
./infinit: fatal error: unexpected HTTP error Bad Gateway pushing volume:
Unknown error
On the latest version from the Debian repo:
infinit --version
0.8.0
I was able to push/fetch user & network without any problems. Only encountering this problem on the volume.
OS Details:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
I tried to install infinit v0.7.3 from repo "https://debian.infinit.sh/ trusty main", Installation went fine but during runtime, I can see there were lot of dependent SOs not loaded...
root@CloudSet-Service-VM-10:/opt/infinit/bin# ldd -v infinit
./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by ./infinit) ./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version
GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libinfinit.so)
./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libaws.so) ./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version
GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libcryptography.so)
./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libelle.so) ./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version
CXXABI_1.3.8' not found (required by /opt/infinit/bin/./../lib/libelle.so)
./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libreactor.so) ./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version
CXXABI_1.3.8' not found (required by /opt/infinit/bin/./../lib/libcrashreporter.so)
./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libboost_program_options.so.1.60.0) ./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version
CXXABI_1.3.8' not found (required by /opt/infinit/bin/./../lib/libboost_filesystem.so.1.60.0)
./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libboost_filesystem.so.1.60.0) ./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version
CXXABI_1.3.8' not found (required by /opt/infinit/bin/./../lib/libboost_regex.so.1.60.0)
./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libboost_regex.so.1.60.0) ./infinit: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version
GLIBCXX_3.4.20' not found (required by /opt/infinit/bin/./../lib/libathena.so)
Please let us know if there are any featured steps required to fix the above.
Thanks,
Syed
I am trying to create a infinit cluster over docker overlay network.
I created swarm cluster and a overlay network. Than created container connected to that network.
docker swarm join...
docker network create --attachable --driver overlay infinit-network
docker run --name infinit-node1 --network infinit-network --privileged -it mefyl/infinit bash
Inside the container I created silo, network and volume.
# infinit silo create --filesystem --name local --capacity 1GB && \
# infinit network create --storage local --name my-network --push && \
# infinit volume create --network my-network --name my-volume --push
Now when I mount that volume, I can edit files and stuff...
# infinit volume mount --name my-volume --mountpoint ~/mnt-alice-volume --allow-root-creation --cache --publish
# echo "this is" > ~/mnt-alice-volume/awesome.txt
# cat ~/mnt-alice-volume/awesome.txt
Now I want to do the same thing on another node of docker swarm cluster. But when I do pretty much the same...
# infinit user login ... && \
# infinit network fetch --name my-network && \
# infinit volume fetch --name my-volume && \
# infinit network link --name my-network
# infinit volume mount --as --name my-volume --mountpoint ~/mnt-alice-volume --allow-root-creation --cache --publish
And try to ls
or cat
the mounted directory, I get
# ls ~/mnt-alice-volume
ls: cannot access '/root/mnt-alice-volume': Input/output error
And the "mount command" says
# infinit volume mount --name my-volume --mountpoint ~/mnt-alice-volume --allow-root-creation --cache --publish
Running network "dominik1/my-network".
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x26eb560): compatibility version 0.7.3
Running volume "dominik1/my-volume".
[infinit.filesystem ] [fuse loop] unexpected exception storing 0x3378cfff631a97c91d22ae709c539e2550f307add5b1f3f0d3ca1200c4792700: no peer available for insertion of 0x3378cfff00
[infinit.filesystem ] [fuse loop] unexpected exception storing 0x32ad45922f441e8daee9f8cfcc86e99c2d6409e643b2b88d2267cd742eba3a00: no peer available for insertion of 0x32ad459200
Am I doing something wrong? Or is this an issue?
I guess it is because the ip of the machine is different in hub and in the overlay network...
When I do
infinit-network run --cache --async --publish //old version, I haven't test on the newest version infinit network yet
Sometimes it causing "unable to find missing block" (on terminal screen), "input/output" error (when I'm trying to access the mount volume), when I disabled both --cache and --async, thing get smooth.
Another problem is, it is unable to delete those (normally would be on /home/myusername/.local/shared/infinit/filesystems/block/...
, when I already delete the files, those block remain and unable to get rid of. (It keep filling up my hard drive).
Any option on this?
Hello,
I have a three device cluster. Each device has its own filesystem silo and joins to a single network that I created with kelips.
The volume creation and mount on all devices succeed, and I can write/read from all three devices to the fuse directory and I see the files in each filesystem. I can read and write to the files on any of the devices and see them on the others.
The issue is if I stop the device that originally did the volume mount with --allow-root-creation then I can't see the files on the other two devices.
I turned on debugging and I see the following messages
2017-Jul-13 23:15:50: [ infinit.model.doughnut.consensus.Paxos ] [fuse loop: get quorum: dht::consensus::PaxosPeer(0x04b497f800)] network exception in paxos: network operation timed out
2017-Jul-13 23:15:50: [ infinit.filesystem ] [fuse loop] unexpected exception fetching 0x990cae5b00("/"): too few peers are available to reach consensus: 0 of 1
Can someone tell me how to get all three devices in the consensus? From the error message it seems as if only the device that created the root block is in the quorum.
Additionally I did see the following failure message, before stopping the root block creating device, but everything seemed to work properly from the replication perspective.
endpoint handshake failure: Handshake failed: incoming peer has same id as us: 0x951ed150d5ea6d3d03b2ed5861c5c33901be197c1025decf1553edd8cc805200
The version is
$ infinit --version
0.8.0
I am failing to get docker volume plugin working. Am I doing something wrong?
Server:
infinit user signup --name dominik2 --fullname "Dominik2" -P "SECRET" --full
export INFINIT_USER=dominik2
infinit silo create --filesystem --name local --capacity 1GB
infinit network create --storage local --name my2-network --push
infinit volume create --network my2-network --name my2-volume
infinit volume mount --name my2-volume --cache --publish --allow-root-creation --mountpoint mnt/shared/
no errors
Client:
infinit user login --name dominik2
export INFINIT_USER=dominik2
infinit network fetch
infinit volume fetch
sudo infinit daemon run --docker-user root
Client output:
infinit daemon run --docker-user root
[cli.daemon] [main] started daemon
[elle.reactor.network.http] [request 0xef2d60] HttpServer(port=0): handle request from 0xef2d60: /VolumeDriver.List {} POST
[elle.reactor.network.http] [request 0xf94e30] HttpServer(port=0): handle request from 0xf94e30: /VolumeDriver.Get {} POST
[elle.reactor.network.http] [request 0xf94be0] HttpServer(port=0): handle request from 0xf94be0: /VolumeDriver.Path {} POST
[elle.reactor.network.http] [request 0xf93fb0] HttpServer(port=0): handle request from 0xf93fb0: /VolumeDriver.Mount {} POST
Running network "dominik2/my2-network".
[infinit.Network] [main] client version: 0.8.0
[infinit.model.Model] [main] infinit::model::Model(0x2d00ed0): compatibility version 0.7.3
[infinit.model.doughnut.Doughnut] [main] Not using UTP although network configuration selects 'all' protocols. UTP has been temporarily deprecated. Force with INFINIT_UTP=1.
[ infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7f94e73d0410): listen on 127.0.0.1:8080
[ infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7f94e73d0410): creation failed, metrics will not be exposed: null context when constructing CivetServer. Possible problem binding to port.
Running volume "dominik2/my2-volume".
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[ infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
The error says, that I need to --allow-root-creation, but it is already allowed on server...
Exactly as title,
When playing around, I accidentally delete alice
locally, and now unable to delete that user from hub anymore. Reading the doc but no clue.
Please help.
Any updates on this? I mean on the roadmap it says it should be done on Q2, but I cant seems to find any news on this.
I have been experimenting with Infinit Desktop inside a Docker container and discovered that I needed to install these dependencies:
$ apt install --no-install-recommends libglib2.0-0 libnss3 libgconf2-4 libfontconfig1 libpangocairo-1.0.0 libxi6 libxcursor1 libxcomposite1 libasound2 libxdamage1 libxtst6 libxrandr2 libgtk2.0-0 libnotify4 libgl1 infinit
Hello,
Is there support for v2 of the S3 signature? We need it for our deployment.
Thank you,
Dustin
Above error is thrown using:
infinit-arm 0.7.3-dev
docker: 17.03.0-ce, build 60ccb22
server:
infinit volume create --as user --network user/net0 --name user/vol0 --allow-root-creation --fuse-option allow_root --cache --async --daemon --push
client:
infinit volume mount --as user --name user/vol0 --allow-root-creation --fuse-option allow_root --cache --async --daemon --mountpoint /home/user/vol0 --publish
daemon on client:
sudo infinit daemon run --as user --docker-user user
docker volume ls on client:
DRIVER VOLUME NAME
infinit user/vol0
docker app on client:
docker run -it --rm --volume-driver infinit -v user/vol0:/mnt hypriot/rpi-alpine ls /mnt
Using infinit 0.7.3 on a CentOS7.3, mounted a volume and set the root as world-writable:
$ infinit acl list --path .
.:
inherit: true
world: rw
fasolti (owner): rw
$ touch one
$ sudo touch two
touch: cannot touch 'two': Permission denied
I though maybe the user must be known by infinit, so I tried to create a root user:
$ infinit user create --name root
Generating RSA keypair.
Locally saved identity for user "root".
$ sudo touch two
touch: cannot touch 'two': Permission denied
Last try was to give explicit permissions to user root:
$ infinit acl set --path . --mode rw --user root
infinit: fatal error: unable to set extended attribute: Invalid argument
What am I doing wrong?
When I try to push a network:
bin/infinit-network --push --as user --name mynet
I obtain this error:
bin/infinit-network: fatal error: unexpected HTTP error Bad Gateway pushing network: Unknown error
If i add a volume to a docker service:
--mount volume-driver=infinit,source=fankserver/teamspeak,target=/data
It will be mounted via deamon:
infinit volume run fankserver/teamspeak --as fankserver --fuse-option allow_root --fetch --push --mountpoint /....
$ infinit volume export --name teamspeak --as fankserver
{"default_permissions":"","mount_options":{"push":true},"name":"fankserver/teamspeak","network":"fankserver/asd"}
I wana change the fuse option "allow_root" -> "allow_other":
infinit volume update --as fankserver --fuse-option allow_other --name teamspeak
The deamon will use the followig and fail:
infinit volume run fankserver/teamspeak --as fankserver --fuse-option allow_root --fuse-option allow_other --fetch --push --mountpoint /....
Because allow_root
and allow_other
can not exists at the same time.
Steps to preproduce:
$ infinit volume create --as fankserver --name test --network cluster --fetch --push
Locally saved volume descriptor "fankserver/test".
Remotely created volume descriptor "fankserver/test".
$ infinit volume mount --as fankserver --publish --allow-root-creation --mountpoint /mnt/infinit --name test
Running network "fankserver/cluster".
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x282e7c0): compatibility version 0.7.3
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on tcp://[::]:33670
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on utp://[::]:33670
Remotely created endpoints for "fankserver/cluster".
Running volume "fankserver/test".
$ cd /mnt/infinit/
$ echo "asd" > a
$ ls
a
$ cat a
asd
^CRemotely deleted endpoints for "fankserver/cluster".
$ /opt/infinit/bin/infinit volume delete --as fankserver --name test --pull --purge
Remotely deleted volume descriptor "fankserver/test".
Locally deleted volume descriptor "fankserver/test".
Locally deleted root block for volume "fankserver/test".
$ /opt/infinit/bin/infinit volume create --as fankserver --name test --network cluster --fetch --push
Locally saved volume descriptor "fankserver/test".
Remotely created volume descriptor "fankserver/test".
$ /opt/infinit/bin/infinit volume mount --as fankserver --publish --allow-root-creation --mountpoint /mnt/infinit --name test
Running network "fankserver/cluster".
[infinit.Network] [main] client version: 0.7.3
[infinit.model.Model] [main] infinit::model::Model(0x166a7c0): compatibility version 0.7.3
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on tcp://[::]:58072
[infinit.model.doughnut.Local] [main] dht::Local(0x0d20819e00): listen on utp://[::]:58072
Remotely created endpoints for "fankserver/cluster".
Running volume "fankserver/test".
$ cd /mnt/infinit/
$ ls
a
$ cat a
asd
Volume content is still there but i deleted and purged it?
How can i recreate a volume with the same name?
Network info:
$ /opt/infinit/bin/infinit network export --as fankserver --name cluster
{"admin_keys":{"group_r":[],"group_w":[],"r":[],"w":[]},"consensus":{"eviction-delay":"10min","replication-factor":2,"type":"paxos"},"name":"fankserver/cluster","overlay":{"rpc_protocol":"all","type":"kouncil"},"owner":{"rsa":"KEY"},"peers":[],"version":"0.7.3"}
As the doc state https://infinit.sh/documentation/reference#introduction
I can understand like: unless you set $INFINIT_HOME, otherwise it will use $HOME
But here are the thing, when I'm using with 'sudo -s', as option -s also said:
-s, --shell
Run the shell specified by the SHELL environment variable if it is set or the shell specified by
the invoking user's password database entry. If a command is specified, it is passed to the shell
for execution via the shell's -c option. If no command is specified, an interactive shell is exe‐
cuted.
As my understanding, it is equivalent to: you are at root privileges but still have your current shell enviroment. (I tried echo $HOME
, and it still /home/myusername
).
But when running with Infinit, eg: infinit-user --create test
Interestingly, it was in /root/.local/share/infinit/filesystem/users/test
, it suppose to in /home/myusername/.local/share/infinit/filesystem/users/test
, right?
infinit user pull
Remotely deleted identity for user "bushbaby123".
not sure if it actually deleted the user, but this does not sound correct
v0.8.0
We have an issue on ubuntu 14.04 with installing infinit package as described here
root@1396bd86f251:/$ apt-get clean
root@1396bd86f251:/$ apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3D2C3B0B
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.O5HKLiPOu2 --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 3D2C3B0B
gpg: requesting key 3D2C3B0B from hkp server keyserver.ubuntu.com
gpg: key 6821EB43: "Infinit <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
root@1396bd86f251:/$ add-apt-repository "deb https://debian.infinit.sh/ trusty main"
root@1396bd86f251:/$ apt-get update -y && apt-get install -y infinit
Ign http://archive.ubuntu.com trusty InRelease
Hit http://archive.ubuntu.com trusty-updates InRelease
Hit http://archive.ubuntu.com trusty-security InRelease
Get:1 https://debian.infinit.sh trusty InRelease
Ign https://debian.infinit.sh trusty InRelease
Hit https://debian.infinit.sh trusty Release.gpg
Hit http://archive.ubuntu.com trusty Release.gpg
Hit https://debian.infinit.sh trusty Release
Hit http://archive.ubuntu.com trusty Release
Hit http://archive.ubuntu.com trusty-updates/main Sources
Hit http://archive.ubuntu.com trusty-updates/restricted Sources
Hit http://archive.ubuntu.com trusty-updates/universe Sources
Hit http://archive.ubuntu.com trusty-updates/main amd64 Packages
Hit http://archive.ubuntu.com trusty-updates/restricted amd64 Packages
Get:2 https://debian.infinit.sh trusty/main amd64 Packages
Hit http://archive.ubuntu.com trusty-updates/universe amd64 Packages
Hit http://archive.ubuntu.com trusty-security/main Sources
Hit http://archive.ubuntu.com trusty-security/restricted Sources
Hit http://archive.ubuntu.com trusty-security/universe Sources
Hit http://archive.ubuntu.com trusty-security/main amd64 Packages
Hit http://archive.ubuntu.com trusty-security/restricted amd64 Packages
Hit http://archive.ubuntu.com trusty-security/universe amd64 Packages
Hit http://archive.ubuntu.com trusty/main Sources
Hit http://archive.ubuntu.com trusty/restricted Sources
Hit http://archive.ubuntu.com trusty/universe Sources
Hit http://archive.ubuntu.com trusty/main amd64 Packages
Hit http://archive.ubuntu.com trusty/restricted amd64 Packages
Hit http://archive.ubuntu.com trusty/universe amd64 Packages
Fetched 2739 B in 10s (259 B/s)
W: Failed to fetch https://debian.infinit.sh/dists/trusty/main/binary-amd64/Packages Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old ones used instead.
--allow-root-creation should be run only once on one host, the root block is created when you use the mounted volumes for the first time.
see also: #15
However in when a mount is not cleaned up properly (kill -9 xxxx or a crash) and restart your mount you might run into the following situation.
tip: use umount /my/mountpoint
to allow for proper house keeping
root@node-2:~# infinit volume mount --name alice-volume --cache --publish --mountpoint /my/mountpoint -d
Running network "alice/alice-network".
[infinit.Network] [main] client version: 0.8.0
[infinit.model.Model] [main] infinit::model::Model(0x284e150): compatibility version 0.8.0
[infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7fe71dbae410): listen on 127.0.0.1:8080
Running volume "alice/swarm-volume".
[ifnt.cli.utility] [main] DETACHING 1 Success
Now an error occur when you try to use the mount...
root@node-2:~# ls /my/mountpoint/
[infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
[infinit.filesystem ] [fuse loop] unable to find root block, allow creation with --allow-root-creation
... message repeats, terminal hangs
So when you follow instruction and start the mount with the --allow-root-creation option and then use the volume you will get errors like these;
root@node-2:~# infinit volume mount --name alice-volume --cache --publish --mountpoint /my/mountpoint --allow-root-creation -d
Running network "alice/alice-network".
[infinit.Network] [main] client version: 0.8.0
[infinit.model.Model] [main] infinit::model::Model(0xfa9180): compatibility version 0.8.0
[infinit.prometheus ] [main] infinit::prometheus::Prometheus(0x7f967311c410): listen on 127.0.0.1:8080
Running volume "alice/alice-volume".
[ifnt.cli.utility] [main] DETACHING 1 Success
root@node-2:~# ls -la /my/mountpoint
[infinit.filesystem ] [fuse loop] refusing to recreate root block, marker set: "/root/.local/state/infinit/filesystem/alice/swarm-network/alice-network/alice-volume/root_block"
[infinit.filesystem ] [fuse loop] refusing to recreate root block, marker set: "/root/.local/state/infinit/filesystem/alice/swarm-network/alice-network/alice-volume/root_block"
... message repeats, terminal hangs
catch 22...
So how do we fix this?
We'll need to run the cleanup properly so this file is removed upon unmounting and it can be properly fetched from the slice-network if it exists.
/root/.local/state/infinit/filesystem/alice/swarm-network/alice-network/alice-volume/root_block
steps
umount /my/mountpoint
infinit volume mount --name swarm-volume --cache --publish --mountpoint /my/mountpoint
without --allow-root-creation
and in foreground (no -d option)control-c
or run umount /my/mountpoint
(do not ls /my/mountpoint
) from a different terminal sessioninfinit volume mount --name alice-volume --cache --publish --mountpoint /my/mountpoint -d
done...
through reading the tutorial, i have created xiaods account. now i want to reset the environment in my devel env, but i can't do it, anyone know howto reset the env to restarting environment.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.