wietsewind / docker-rippled Goto Github PK

View Code? Open in Web Editor NEW

59.0 7.0 34.0 87 KB

Run XRP Ledger (rippled) node in a Docker container

Home Page: https://hub.docker.com/r/xrpllabsofficial/xrpld

License: MIT License

Shell 62.88% Dockerfile 37.12%

xrp-ledger

docker-rippled's Introduction

Rippled (node)

This container allows you to run a rippled node. No config required.

The server will keep a history of only 256 ledgers. You can change this value in the config (more about the config in this readme).

The container is configured to serve a public http websocket at port 80 and the local rpc admin service in the container at port 5005. Other ports (443, 6006, 51235) can be mapped but should be enabled in the config first.

This container is running on ubuntu:latest.

How to run

From Github

If you downloaded / cloned the Github repo you got yourself a few scripts to get started. In the ./go folder, the following scripts are available, run:

go/build to build the container image (tag: rippled)
go/up to create a new container named rippled and setup the port and persistent config (*1)
go/down to stop and remove the container rippled

The go/up command will mount the subfolder (in the cloned repo folder) config to the container; the rippled.cfg config and validators.txt will be loaded from this folder when rippled starts. If you stop/start or restart the container, the container will pickup your changes.

When starting the container the go/up script will map port 80 on your host to port 80 in the container. This is where rippled is configured to serve a websocket. If you want to run the websocket on another TCP port, you can enter the port after the go/up command, eg.:

go/up 8080

After spinning the container up, you will see the rippled log. You should see a lot of information show up within a few seconds. If you want to stop watching the log, press CTRL - C. The container will keep on running in the background.

If you want to build the image manually, use (you can change the tag):

docker build --tag rippled:latest .

From the Docker Hub

Use the image xrpllabsofficial/xrpld.

Because you only retrieved the container image from the Docker Hub, you have to manually create a container based on the image. When creating the container, please make sure you open port 80.

If you run the container with a mapping to /config/ (in the container) containing a rippled.cfg and validators.txt file, these will be used. If the mapping or these files aren't present, rippled will start with the default config.

This command launches your rippled container and the rippled websocket at port 80:

docker run -dit \
    --name rippled \
    -p 80:80 \
    -v /my/local/disk/xrpld-config/:/config/ \
    xrpllabsofficial/xrpld:latest

You can change the --name and make sure you specify a valid local full path for your volume source, instead of /my/local/disk/xrpld-config/.

You can fetch a working sample config from the Github repo.

Note on Apple M1 / M2 chips:

Run the container with --platform linux/amd64 to get it to work on your Mac M1 / M2.

Passing arguments/environment variables

Both environment variables passed with -e to docker run and arguments added at the end of the docker run command will be passed. E.g.:

docker run \
  -e TESTVAR=123123 \
  -it --name rippled -p $PORT:80 \
  -v $(pwd)/../config:/config/ \
  xrpllabsofficial/xrpld:latest \
  -a \
  --start

... will pass the environment variable TESTVAR with value, and the arguments -aaa and -c to rippled.

Alternatively, if you can't pass direct arguments, you can pass a string of arguments as an environment variable called ENV_ARGS, like this:

docker run \
  -e ENV_ARGS="-a --start" \
  -it --name rippled -p $PORT:80 \
  -v $(pwd)/../config:/config/ \
  xrpllabsofficial/xrpld:latest

So it's running

If you want to check the rippled-logs (container stdout, press CTRL - C to stop watching):

docker logs -f rippled

If you want to check the rippled server status:

docker exec rippled rippled server_info

Check the value of complete_ledgers in the server info to see if the server has complete ledgers with transactions. When you launch the container it may take a few minutes for the server to sync.

If you started the container manually, you may have to change the name of the container (rippled) to the name you entered in your docker run command.

Connecting

You can now connect to the rippled websocket using a client like xrpl.js.

Updating

2018-02-21 rippled 0.90.0 is released
2018-03-23 rippled 0.90.1 is released
2018-05-15 rippled 1.0.0 is released
2018-06-14 rippled 1.0.1 is released
2018-09-15 rippled 1.1.0 is released
2018-10-23 rippled 1.1.1 is released
2018-12-12 rippled 1.1.2 is released
2019-02-14 rippled 1.2.0 is released
2019-02-27 rippled 1.2.1 is released
2019-03-07 rippled 1.2.2 is released
2019-04-03 rippled 1.2.3 is released
2019-04-17 rippled 1.2.4 is released
2019-07-26 rippled 1.3.1 is released
2019-07-26 rippled 1.4.0 is released
2020-04-01 rippled 1.5.0 is released
2020-08-19 rippled 1.6.0 is released
2021-05-24 rippled 1.7.2 is released
2021-08-28 rippled 1.7.3 is released
2021-12-02 rippled 1.8.1 is released
2022-01-14 rippled 1.8.4 is released
2022-02-08 rippled 1.8.5 is released
2022-04-07 rippled 1.9.0 is released
2022 rippled 1.9.2 is released
2022 rippled 1.9.3 is released
2022 rippled 1.9.4 is released
2023-03-14 rippled 1.10.0 is released
2023-03 rippled 1.10.1 is released
2023-06-27 rippled 1.11.0 is released
2023-09-06 rippled 1.12.0 is released
2024-01-09 rippled 2.0.0 is released
2024-01-29 rippled 2.0.1 is released
2024-02-20 rippled 2.1.0 is released
2024-03-27 rippled 2.1.1 is released
2024-06-05 rippled 2.2.0 is released

Update process

Stop the container: docker stop rippled (if you named (--name) the container rippled)
Remove the container: docker rm rippled
Remove the image: docker rmi xrpllabsofficial/xrpld:latest (or if you built the container image based on the Github repo: use the image name you specified when building)
Re-create the container; if you used Git: git pull and go/build - if you used the Docker Hub: just use the command from this Readme (From the Docker Hub), a new version of the image will be downloaded.

USE THE PATHS YOU SPECIFIED (-v argument) WHEN RECREATING THE CONTAINER IF YOU WANT TO KEEP YOUR CONFIG AND/OR DATA!

Building & publishing to Docker Hub:

version=2.2.0 # Sample
docker build --platform linux/amd64 --no-cache --tag xrpllabsofficial/xrpld:$version .
docker push xrpllabsofficial/xrpld:$version
docker tag xrpllabsofficial/xrpld:$version xrpllabsofficial/xrpld:latest
docker push xrpllabsofficial/xrpld:latest

docker-rippled's People

Contributors

Stargazers

Watchers

docker-rippled's Issues

why it is so slow to sync Ripple Node ???

I take several days to sync the ledgers，there are 20 thousand + ledgers on my node, but there are 40 million + ledgers on the main net now. 😭 Is there any way to speed up it ? Thx 🤝
my critical config as follows:

rippled.cfg

[port_peer]
port = 51235
ip = 0.0.0.0
protocol = peer

[node_size]
small

[node_db]
type=NuDB
path=/var/lib/rippled/db/nudb
advisory_delete=0
online_delete=256

[ledger_history]
256

[ips]
r.ripple.com 51235

validators.txt

[validator_list_sites]
https://vl.ripple.com

[validator_list_keys]
ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734

Submitting a transaction gives amendmentBlocked

Hey. When I submit a transaction I get an error message stating: "error_message": "Amendment blocked, need upgrade.",

I am using the test net. Here are the calls I am making:
{ "method": "submit", "params": [ { "offline": false, "secret": "shb2MeSPMjbk4bTGFWjckU2WkuwbU", "tx_json": { "Account": "rnGkgVq1d1TbSRbEKn4LYuphuHitoDsLD2", "Amount": "199", "Destination": "rGEj2VrKC1AKRXMcHkrcZcTy2Q2iL8eVSP", "TransactionType": "Payment" }, "fee_mult_max": 1000 } ] }

I get this response:

{ "result": { "error": "amendmentBlocked", "error_code": 14, "error_message": "Amendment blocked, need upgrade.", "request": { "command": "submit", "fee_mult_max": 1000, "offline": false, "secret": "<masked>", "tx_json": { "Account": "rnGkgVq1d1TbSRbEKn4LYuphuHitoDsLD2", "Amount": "199", "Destination": "rGEj2VrKC1AKRXMcHkrcZcTy2Q2iL8eVSP", "TransactionType": "Payment" } }, "status": "error" } }

Why is the capacity of containers increasing?

I am operating a Ripple node through Docker.

Create a container as shown below.
"docker run -itd --name xrp_testnet -p 40041:5005 -p 40042:51235 -p 40043:80 -p 40044:51234 -p 40045:6006 -p 40046:50051 -p 40047:443 -v /home/docker /container/testnet/xrp/xrp_testnet/config:/etc/opt/ripple/ -v /home/docker/container/testnet/xrp/xrp_testnet/db:/var/lib/rippled/db -v /home/docker/ container/testnet/xrp/xrp_testnet/log:/var/log/rippled xrpllabsofficial/xrpld:latest"

There is a problem.
Even though I mounted it and removed Ripple's logs and block data, the container's capacity continues to increase.

Why is the capacity of containers increasing?

[root@localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 63G 0 63G 0% /dev
tmpfs 63G 0 63G 0% /dev/shm
tmpfs 63G 18M 63G 1% /run
tmpfs 63G 0 63G 0% /sys/fs/cgroup
/dev/mapper/centos-root 50G 49G 1.6G 97% /
/dev/sda2 1014M 332M 683M 33% /boot
/dev/sda1 200M 12M 189M 6% /boot/efi
/dev/mapper/centos-home 12T 4.9T 6.5T 43% /home
tmpfs 13G 0 13G 0% /run/user/0
overlay 50G 49G 1.6G 97% /var/lib/docker/overlay2/786417a4 b8e162ad0c00353c835eb62d894d8249fe03181389bfab904f83723d/merged
overlay 50G 49G 1.6G 97% /var/lib/docker/overlay2/239c0652 f33579598b9b246e1400cb85b0fd0256494b277c7dbdbd352a61b1b5/merged
overlay 50G 49G 1.6G 97% /var/lib/docker/overlay2/36db05b6 7f7ae64fdf06fa6192b7864a756a4748b12406c32d0ac6bacf20fab6/merged

As you can see here, the /dev/mapper/centos-root capacity continues to increase and the container seems to stop.
I'm curious about the cause.

Thank you for reading this long content!!

Mapping config directory on Centos

chcon -Rt svirt_sandbox_file_t ./config required to allow the container to get the config from the parent host.

tx_blob data question

hello.
I am writing because I have a question.
I have now created a key pair offline and signed the transaction.
A signature was received,
I am trying to create a blob and make a submit RPC call.
Here is the question.
Can the tx_blob value be made into a signature value?
I want to create a tx_blob.
I knew that the signature value was converted to tx_blob (gpt told me).
But maybe I was wrong?

Startup param `--net` is depricated

https://xrpl.org/commandline-usage.html#daemon-mode-options

# Start rippled, Passthrough other arguments
exec /opt/ripple/bin/rippled --net --conf /etc/opt/ripple/rippled.cfg "$@"

https://github.com/WietseWind/docker-rippled/blob/master/entrypoint#L18

"validated": false??

hello!
I want to enable “destination Tag”.
I want to make "requireDestinationTag": true.
I followed it by referring to (https://xrpl.org/require-destination-tags.html).

I created and sent a tx...
"requireDestinationTag": does not change to true.
result

{{ "accepted": true, "account_sequence_available": 43891710, "account_sequence_next": 43891710, "applied": true, "broadcast": true, "engine_result": "tesSUCCESS", "engine_result_code": 0, "result_message": "The transaction was applied. Only final in a validated ledger.", "kept": true, "open_ledger_cost": "10", "queued": false, "status": "success", "tx_blob": "", "tx_json": { "Account": "rGG9k2shfmrYsuoonsDLjUgNUugfL72Ps6", "Fee": "12", "Flags": 2147483648, "LastLedgerSequence": 43893466, "Memos": [ { "Memo": { "MemoData": "7B2270617468 223A222F726571756972652D64657374696E6174696F6E2D746167732E68746D6C222C22627574746F6E223A2273656E642D6163636F756E74736574222C2 273746570223A332C22746F74616C7374657073223A367D ", "MemoFormat": "6170706C69636174696F6E2F6A736F6E", "MemoType": "68747470733A2F2F6769746875622E636F6D2F5852504C462F7872706C2D6465762D706F7 274616C2F626C6F622F6D61737465722F746F6F6C2F494E5445524143544956455F5455544F5249414C535F524541444D452E6D64" } } ], "Sequence": 43891709 , "SetFlag": 1, "SigningPubKey": "ED0003A38942BDBE5F18F6EFD762DFDD6E69D86B25C69677F5E54D1B5876E47CAD", "TransactionType": "AccountSet", " TxnSignature": "B6DF28E3089A19CB8C6E16AA82C00797E0C3A5B991ABCCA52B92F3B1A4155E312842E2E1C6D39CB5FE671447899DC29B767710F0AFC5C4C36159D22D5A0BC9 00", "hash": "97925FDDABAA10632A1D5CEA2507F14C7927198BBEF9402609E07B80F95B3F65" }, "validated_ledger_index": 43893465}}

It comes out like this...
One thing I guess is that when I looked up the hash, it was “validated”: false.
What can I do to solve this problem? I need help.
Maybe I did something wrong in the config file?

<rippled.cfg>

[server]
port_rpc_admin_local
port_ws_public
port_peer

[port_rpc_admin_local]
port = 5005
ip = 0.0.0.0
admin = 127.0.0.1
protocol = http

[port_ws_public]
port = 80
ip = 0.0.0.0
protocol = ws

[port_peer]
port = 51235
ip = 0.0.0.0
protocol = peer


[node_db]
type=NuDB
path=/var/lib/rippled/db/nudb

[ledger_history]
full

[database_path]
/var/lib/rippled/db

[signing_support]
true

[debug_logfile]
/var/log/rippled/debug.log

[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org

[ips]
s.altnet.rippletest.net 51235

[ips_fixed]
169.55.164.20 51235
50.22.123.215 51235

[import_db]
type=NuDB
path=/tmp/full_history_dump/

[validators_file]
validators.txt

[rpc_startup]
{
    "command": "log_level",
    "severity": "info",
}

[rpc_admin]
admin = 0.0.0.0

[ssl_verify]
1

Dear developer, please help me!

Dear developer,

Currently, while I was receiving node blocks, my computer crashed, so I rebooted and ran it again, but the blocks did not crash.

I have one question!
Currently, I am running a Ripple node.
But isn't there a site where Ripple can get full node snapshots?
Tron and other coins exist, but does Ripple not exist?

The TX that was viewed just a moment ago cannot be viewed.

hello!
I am posting a question because I have a question while operating the node.
We are currently operating a testnet through Docker.
We created a TX through our node and called submit RPC.
TX information was confirmed through the TX PRC function.
however!!
Shockingly, we searched with our TX hash on the "https://blockexplorer" site, but it did not work.... ㅡ0ㅡ
And after some time, we called the TX RPC function with our node... and the TX that was queried was

{
     "result": {
         "error": "txnNotFound",
         "error_code": 29,
         "error_message": "Transaction not found.",
         "request": {
             "binary": false,
             "command": "tx",
             "transaction": "A9EAE77170075FAD7491B6795FD6BF7DFCFEB13F952B2694D5FDA14A7FAB1AB0"
         },
         "status": "error"
     }
}

It said that it couldn't be found as above...
Why is TX, which was clearly viewable, suddenly not viewable?
What is the reason?
Developer Ko Soo, please. I am very curious about the reason.
Thank you for reading this long article.

Failed go/build

❯ l
total 56
drwxr-xr-x  11 mbergen  staff   352B Jun 26 16:28 .
drwxr-xr-x  11 mbergen  staff   352B Jun 26 14:48 ..
-rw-r--r--@  1 mbergen  staff   6.0K Jun  9 08:21 .DS_Store
drwxr-xr-x  12 mbergen  staff   384B Jun 26 16:36 .git
-rw-r--r--   1 mbergen  staff     0B Jun  6 11:44 .gitignore
-rw-r--r--   1 mbergen  staff   1.1K Jun  9 07:08 Dockerfile
-rw-r--r--   1 mbergen  staff   1.0K Jun  6 11:44 LICENSE
-rw-r--r--   1 mbergen  staff   7.8K Jun 26 16:28 README.md
drwxr-xr-x   4 mbergen  staff   128B Jun 12 13:40 config
-rwxr-xr-x   1 mbergen  staff   749B Jun  6 11:44 entrypoint
drwxr-xr-x   5 mbergen  staff   160B Jun 26 16:30 go

❯ go/build
Stopping containers
15d2e59224d3
Building image
[+] Building 23.8s (8/9)
 => [internal] load .dockerignore                                                                                                                                    0.0s
 => => transferring context: 2B                                                                                                                                      0.0s
 => [internal] load build definition from Dockerfile                                                                                                                 0.0s
 => => transferring dockerfile: 1.16kB                                                                                                                               0.0s
 => [internal] load metadata for docker.io/library/ubuntu:latest                                                                                                     3.2s
 => CACHED [1/5] FROM docker.io/library/ubuntu:latest@sha256:6120be6a2b7ce665d0cbddc3ce6eae60fe94637c6a66985312d1f02f63cc0bcd                                        0.0s
 => [internal] load build context                                                                                                                                    0.0s
 => => transferring context: 32B                                                                                                                                     0.0s
 => [2/5] RUN export LANGUAGE=C.UTF-8; export LANG=C.UTF-8; export LC_ALL=C.UTF-8; export DEBIAN_FRONTEND=noninteractive                                             0.1s
 => [3/5] COPY entrypoint /entrypoint.sh                                                                                                                             0.0s
 => ERROR [4/5] RUN apt-get update -y &&     apt-get install apt-transport-https ca-certificates wget gnupg -y &&     mkdir -p /usr/local/share/keyrings/ &&     w  20.5s
------
 > [4/5] RUN apt-get update -y &&     apt-get install apt-transport-https ca-certificates wget gnupg -y &&     mkdir -p /usr/local/share/keyrings/ &&     wget -q -O - "https://repos.ripple.com/repos/api/gpg/key/public" | gpg --dearmor > ripple-key.gpg &&     mv ripple-key.gpg /usr/local/share/keyrings &&     echo "deb [signed-by=/usr/local/share/keyrings/ripple-key.gpg] https://repos.ripple.com/repos/rippled-deb focal stable" | tee -a /etc/apt/sources.list.d/ripple.list &&     apt-get update -y &&     apt-get install rippled -y &&     rm -rf /var/lib/apt/lists/* &&     export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/ripple/bin/ &&     chmod +x /entrypoint.sh &&     echo '#!/bin/bash' > /usr/bin/server_info && echo '/entrypoint.sh server_info' >> /usr/bin/server_info &&     chmod +x /usr/bin/server_info:
#0 0.739 Get:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease [270 kB]
#0 1.937 Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [119 kB]
#0 2.238 Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [108 kB]
#0 2.739 Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
#0 3.017 Get:5 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages [17.2 MB]
#0 6.883 Get:6 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages [24.2 kB]
#0 6.883 Get:7 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages [1758 kB]
#0 6.887 Get:8 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages [224 kB]
#0 6.905 Get:9 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse arm64 Packages [22.9 kB]
#0 6.908 Get:10 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64 Packages [296 kB]
#0 6.950 Get:11 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages [845 kB]
#0 7.397 Get:12 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 Packages [1069 kB]
#0 8.660 Get:13 http://ports.ubuntu.com/ubuntu-ports jammy-backports/main arm64 Packages [49.0 kB]
#0 8.667 Get:14 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64 Packages [23.6 kB]
#0 8.668 Get:15 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 Packages [821 kB]
#0 8.758 Get:16 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64 Packages [295 kB]
#0 8.839 Get:17 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages [564 kB]
#0 8.899 Get:18 http://ports.ubuntu.com/ubuntu-ports jammy-security/multiverse arm64 Packages [18.7 kB]
#0 8.932 Fetched 23.8 MB in 9s (2767 kB/s)
#0 8.932 Reading package lists...
#0 9.377 Reading package lists...
#0 9.785 Building dependency tree...
#0 9.864 Reading state information...
#0 9.943 The following additional packages will be installed:
#0 9.943   dirmngr gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server
#0 9.943   gpgconf gpgsm libassuan0 libksba8 libldap-2.5-0 libldap-common libnpth0
#0 9.943   libpsl5 libreadline8 libsasl2-2 libsasl2-modules libsasl2-modules-db
#0 9.943   libsqlite3-0 openssl pinentry-curses publicsuffix readline-common
#0 9.943 Suggested packages:
#0 9.943   dbus-user-session libpam-systemd pinentry-gnome3 tor parcimonie xloadimage
#0 9.943   scdaemon libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimdal
#0 9.943   libsasl2-modules-ldap libsasl2-modules-otp libsasl2-modules-sql pinentry-doc
#0 9.943   readline-doc
#0 9.978 The following NEW packages will be installed:
#0 9.978   apt-transport-https ca-certificates dirmngr gnupg gnupg-l10n gnupg-utils gpg
#0 9.978   gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm libassuan0 libksba8
#0 9.978   libldap-2.5-0 libldap-common libnpth0 libpsl5 libreadline8 libsasl2-2
#0 9.978   libsasl2-modules libsasl2-modules-db libsqlite3-0 openssl pinentry-curses
#0 9.978   publicsuffix readline-common wget
#0 10.34 0 upgraded, 28 newly installed, 0 to remove and 1 not upgraded.
#0 10.34 Need to get 5327 kB of archives.
#0 10.34 After this operation, 13.0 MB of additional disk space will be used.
#0 10.34 Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 openssl arm64 3.0.2-0ubuntu1.10 [1164 kB]
#0 11.73 Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 ca-certificates all 20230311ubuntu0.22.04.1 [155 kB]
#0 11.77 Get:3 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 readline-common all 8.1.2-1 [53.5 kB]
#0 11.78 Get:4 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 libreadline8 arm64 8.1.2-1 [153 kB]
#0 11.79 Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 libsqlite3-0 arm64 3.37.2-2ubuntu0.1 [636 kB]
#0 11.90 Get:6 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 libpsl5 arm64 0.21.0-1.2build2 [58.3 kB]
#0 11.90 Get:7 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 publicsuffix all 20211207.1025-1 [129 kB]
#0 11.95 Get:8 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 wget arm64 1.21.2-2ubuntu1 [364 kB]
#0 11.99 Get:9 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 apt-transport-https all 2.4.9 [1510 B]
#0 11.99 Get:10 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 libassuan0 arm64 2.5.5-1build1 [36.5 kB]
#0 11.99 Get:11 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gpgconf arm64 2.2.27-3ubuntu2.1 [92.5 kB]
#0 12.33 Get:12 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 libksba8 arm64 1.6.0-2ubuntu0.2 [117 kB]
#0 13.08 Get:13 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 libsasl2-modules-db arm64 2.1.27+dfsg2-3ubuntu1.2 [21.1 kB]
#0 13.10 Get:14 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 libsasl2-2 arm64 2.1.27+dfsg2-3ubuntu1.2 [55.6 kB]
#0 13.16 Get:15 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 libldap-2.5-0 arm64 2.5.14+dfsg-0ubuntu0.22.04.2 [181 kB]
#0 13.38 Get:16 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 libnpth0 arm64 1.6-3build2 [8156 B]
#0 13.39 Get:17 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 dirmngr arm64 2.2.27-3ubuntu2.1 [289 kB]
#0 13.54 Get:18 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gnupg-l10n all 2.2.27-3ubuntu2.1 [54.4 kB]
#0 13.56 Get:19 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gnupg-utils arm64 2.2.27-3ubuntu2.1 [304 kB]
#0 13.65 Get:20 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gpg arm64 2.2.27-3ubuntu2.1 [506 kB]
#0 13.79 Get:21 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 pinentry-curses arm64 1.1.1-1build2 [33.5 kB]
#0 13.79 Get:22 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gpg-agent arm64 2.2.27-3ubuntu2.1 [204 kB]
#0 14.21 Get:23 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gpg-wks-client arm64 2.2.27-3ubuntu2.1 [61.4 kB]
#0 14.91 Get:24 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gpg-wks-server arm64 2.2.27-3ubuntu2.1 [56.8 kB]
#0 15.03 Get:25 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gpgsm arm64 2.2.27-3ubuntu2.1 [192 kB]
#0 15.36 Get:26 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 gnupg all 2.2.27-3ubuntu2.1 [315 kB]
#0 15.60 Get:27 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 libldap-common all 2.5.14+dfsg-0ubuntu0.22.04.2 [15.8 kB]
#0 15.61 Get:28 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 libsasl2-modules arm64 2.1.27+dfsg2-3ubuntu1.2 [68.4 kB]
#0 16.00 debconf: delaying package configuration, since apt-utils is not installed
#0 16.02 Fetched 5327 kB in 6s (907 kB/s)
#0 16.03 Selecting previously unselected package openssl.
(Reading database ... 4389 files and directories currently installed.)
#0 16.05 Preparing to unpack .../00-openssl_3.0.2-0ubuntu1.10_arm64.deb ...
#0 16.05 Unpacking openssl (3.0.2-0ubuntu1.10) ...
#0 16.08 Selecting previously unselected package ca-certificates.
#0 16.08 Preparing to unpack .../01-ca-certificates_20230311ubuntu0.22.04.1_all.deb ...
#0 16.08 Unpacking ca-certificates (20230311ubuntu0.22.04.1) ...
#0 16.11 Selecting previously unselected package readline-common.
#0 16.11 Preparing to unpack .../02-readline-common_8.1.2-1_all.deb ...
#0 16.12 Unpacking readline-common (8.1.2-1) ...
#0 16.13 Selecting previously unselected package libreadline8:arm64.
#0 16.13 Preparing to unpack .../03-libreadline8_8.1.2-1_arm64.deb ...
#0 16.14 Unpacking libreadline8:arm64 (8.1.2-1) ...
#0 16.15 Selecting previously unselected package libsqlite3-0:arm64.
#0 16.15 Preparing to unpack .../04-libsqlite3-0_3.37.2-2ubuntu0.1_arm64.deb ...
#0 16.15 Unpacking libsqlite3-0:arm64 (3.37.2-2ubuntu0.1) ...
#0 16.17 Selecting previously unselected package libpsl5:arm64.
#0 16.17 Preparing to unpack .../05-libpsl5_0.21.0-1.2build2_arm64.deb ...
#0 16.17 Unpacking libpsl5:arm64 (0.21.0-1.2build2) ...
#0 16.19 Selecting previously unselected package publicsuffix.
#0 16.19 Preparing to unpack .../06-publicsuffix_20211207.1025-1_all.deb ...
#0 16.19 Unpacking publicsuffix (20211207.1025-1) ...
#0 16.20 Selecting previously unselected package wget.
#0 16.20 Preparing to unpack .../07-wget_1.21.2-2ubuntu1_arm64.deb ...
#0 16.21 Unpacking wget (1.21.2-2ubuntu1) ...
#0 16.22 Selecting previously unselected package apt-transport-https.
#0 16.22 Preparing to unpack .../08-apt-transport-https_2.4.9_all.deb ...
#0 16.22 Unpacking apt-transport-https (2.4.9) ...
#0 16.24 Selecting previously unselected package libassuan0:arm64.
#0 16.24 Preparing to unpack .../09-libassuan0_2.5.5-1build1_arm64.deb ...
#0 16.24 Unpacking libassuan0:arm64 (2.5.5-1build1) ...
#0 16.25 Selecting previously unselected package gpgconf.
#0 16.25 Preparing to unpack .../10-gpgconf_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.25 Unpacking gpgconf (2.2.27-3ubuntu2.1) ...
#0 16.27 Selecting previously unselected package libksba8:arm64.
#0 16.27 Preparing to unpack .../11-libksba8_1.6.0-2ubuntu0.2_arm64.deb ...
#0 16.27 Unpacking libksba8:arm64 (1.6.0-2ubuntu0.2) ...
#0 16.28 Selecting previously unselected package libsasl2-modules-db:arm64.
#0 16.28 Preparing to unpack .../12-libsasl2-modules-db_2.1.27+dfsg2-3ubuntu1.2_arm64.deb ...
#0 16.28 Unpacking libsasl2-modules-db:arm64 (2.1.27+dfsg2-3ubuntu1.2) ...
#0 16.30 Selecting previously unselected package libsasl2-2:arm64.
#0 16.30 Preparing to unpack .../13-libsasl2-2_2.1.27+dfsg2-3ubuntu1.2_arm64.deb ...
#0 16.30 Unpacking libsasl2-2:arm64 (2.1.27+dfsg2-3ubuntu1.2) ...
#0 16.31 Selecting previously unselected package libldap-2.5-0:arm64.
#0 16.31 Preparing to unpack .../14-libldap-2.5-0_2.5.14+dfsg-0ubuntu0.22.04.2_arm64.deb ...
#0 16.31 Unpacking libldap-2.5-0:arm64 (2.5.14+dfsg-0ubuntu0.22.04.2) ...
#0 16.33 Selecting previously unselected package libnpth0:arm64.
#0 16.33 Preparing to unpack .../15-libnpth0_1.6-3build2_arm64.deb ...
#0 16.33 Unpacking libnpth0:arm64 (1.6-3build2) ...
#0 16.35 Selecting previously unselected package dirmngr.
#0 16.35 Preparing to unpack .../16-dirmngr_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.36 Unpacking dirmngr (2.2.27-3ubuntu2.1) ...
#0 16.37 Selecting previously unselected package gnupg-l10n.
#0 16.38 Preparing to unpack .../17-gnupg-l10n_2.2.27-3ubuntu2.1_all.deb ...
#0 16.38 Unpacking gnupg-l10n (2.2.27-3ubuntu2.1) ...
#0 16.39 Selecting previously unselected package gnupg-utils.
#0 16.39 Preparing to unpack .../18-gnupg-utils_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.39 Unpacking gnupg-utils (2.2.27-3ubuntu2.1) ...
#0 16.41 Selecting previously unselected package gpg.
#0 16.41 Preparing to unpack .../19-gpg_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.41 Unpacking gpg (2.2.27-3ubuntu2.1) ...
#0 16.43 Selecting previously unselected package pinentry-curses.
#0 16.43 Preparing to unpack .../20-pinentry-curses_1.1.1-1build2_arm64.deb ...
#0 16.43 Unpacking pinentry-curses (1.1.1-1build2) ...
#0 16.45 Selecting previously unselected package gpg-agent.
#0 16.45 Preparing to unpack .../21-gpg-agent_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.45 Unpacking gpg-agent (2.2.27-3ubuntu2.1) ...
#0 16.46 Selecting previously unselected package gpg-wks-client.
#0 16.46 Preparing to unpack .../22-gpg-wks-client_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.47 Unpacking gpg-wks-client (2.2.27-3ubuntu2.1) ...
#0 16.48 Selecting previously unselected package gpg-wks-server.
#0 16.48 Preparing to unpack .../23-gpg-wks-server_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.49 Unpacking gpg-wks-server (2.2.27-3ubuntu2.1) ...
#0 16.50 Selecting previously unselected package gpgsm.
#0 16.50 Preparing to unpack .../24-gpgsm_2.2.27-3ubuntu2.1_arm64.deb ...
#0 16.50 Unpacking gpgsm (2.2.27-3ubuntu2.1) ...
#0 16.51 Selecting previously unselected package gnupg.
#0 16.52 Preparing to unpack .../25-gnupg_2.2.27-3ubuntu2.1_all.deb ...
#0 16.52 Unpacking gnupg (2.2.27-3ubuntu2.1) ...
#0 16.53 Selecting previously unselected package libldap-common.
#0 16.53 Preparing to unpack .../26-libldap-common_2.5.14+dfsg-0ubuntu0.22.04.2_all.deb ...
#0 16.53 Unpacking libldap-common (2.5.14+dfsg-0ubuntu0.22.04.2) ...
#0 16.55 Selecting previously unselected package libsasl2-modules:arm64.
#0 16.55 Preparing to unpack .../27-libsasl2-modules_2.1.27+dfsg2-3ubuntu1.2_arm64.deb ...
#0 16.55 Unpacking libsasl2-modules:arm64 (2.1.27+dfsg2-3ubuntu1.2) ...
#0 16.57 Setting up libksba8:arm64 (1.6.0-2ubuntu0.2) ...
#0 16.57 Setting up libpsl5:arm64 (0.21.0-1.2build2) ...
#0 16.57 Setting up wget (1.21.2-2ubuntu1) ...
#0 16.58 Setting up apt-transport-https (2.4.9) ...
#0 16.58 Setting up libsqlite3-0:arm64 (3.37.2-2ubuntu0.1) ...
#0 16.59 Setting up libsasl2-modules:arm64 (2.1.27+dfsg2-3ubuntu1.2) ...
#0 16.59 Setting up libnpth0:arm64 (1.6-3build2) ...
#0 16.60 Setting up libassuan0:arm64 (2.5.5-1build1) ...
#0 16.60 Setting up libldap-common (2.5.14+dfsg-0ubuntu0.22.04.2) ...
#0 16.60 Setting up libsasl2-modules-db:arm64 (2.1.27+dfsg2-3ubuntu1.2) ...
#0 16.61 Setting up gnupg-l10n (2.2.27-3ubuntu2.1) ...
#0 16.61 Setting up libsasl2-2:arm64 (2.1.27+dfsg2-3ubuntu1.2) ...
#0 16.61 Setting up openssl (3.0.2-0ubuntu1.10) ...
#0 16.62 Setting up readline-common (8.1.2-1) ...
#0 16.62 Setting up publicsuffix (20211207.1025-1) ...
#0 16.63 Setting up pinentry-curses (1.1.1-1build2) ...
#0 16.64 Setting up libreadline8:arm64 (8.1.2-1) ...
#0 16.64 Setting up libldap-2.5-0:arm64 (2.5.14+dfsg-0ubuntu0.22.04.2) ...
#0 16.64 Setting up ca-certificates (20230311ubuntu0.22.04.1) ...
#0 16.69 debconf: unable to initialize frontend: Dialog
#0 16.69 debconf: (TERM is not set, so the dialog frontend is not usable.)
#0 16.69 debconf: falling back to frontend: Readline
#0 16.69 debconf: unable to initialize frontend: Readline
#0 16.69 debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.34.0 /usr/local/share/perl/5.34.0 /usr/lib/aarch64-linux-gnu/perl5/5.34 /usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl-base /usr/lib/aarch64-linux-gnu/perl/5.34 /usr/share/perl/5.34 /usr/local/lib/site_perl) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
#0 16.69 debconf: falling back to frontend: Teletype
#0 17.06 Updating certificates in /etc/ssl/certs...
#0 17.58 137 added, 0 removed; done.
#0 17.59 Setting up gpgconf (2.2.27-3ubuntu2.1) ...
#0 17.60 Setting up gpg (2.2.27-3ubuntu2.1) ...
#0 17.60 Setting up gnupg-utils (2.2.27-3ubuntu2.1) ...
#0 17.60 Setting up gpg-agent (2.2.27-3ubuntu2.1) ...
#0 17.84 Setting up gpgsm (2.2.27-3ubuntu2.1) ...
#0 17.85 Setting up dirmngr (2.2.27-3ubuntu2.1) ...
#0 17.91 Setting up gpg-wks-server (2.2.27-3ubuntu2.1) ...
#0 17.92 Setting up gpg-wks-client (2.2.27-3ubuntu2.1) ...
#0 17.92 Setting up gnupg (2.2.27-3ubuntu2.1) ...
#0 17.92 Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
#0 17.95 Processing triggers for ca-certificates (20230311ubuntu0.22.04.1) ...
#0 17.96 Updating certificates in /etc/ssl/certs...
#0 18.33 0 added, 0 removed; done.
#0 18.33 Running hooks in /etc/ca-certificates/update.d...
#0 18.34 done.
#0 18.54 deb [signed-by=/usr/local/share/keyrings/ripple-key.gpg] https://repos.ripple.com/repos/rippled-deb focal stable
#0 18.73 Get:1 https://repos.ripple.com/repos/rippled-deb focal InRelease [17.6 kB]
#0 18.93 Hit:2 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
#0 19.10 Hit:3 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
#0 19.27 Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
#0 19.44 Hit:5 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
#0 19.51 Fetched 17.6 kB in 1s (19.0 kB/s)
#0 19.51 Reading package lists...
#0 19.93 Reading package lists...
#0 20.32 Building dependency tree...
#0 20.40 Reading state information...
#0 20.41 E: Unable to locate package rippled
------
Dockerfile:9
--------------------
   8 |
   9 | >>> RUN apt-get update -y && \
  10 | >>>     apt-get install apt-transport-https ca-certificates wget gnupg -y && \
  11 | >>>     mkdir -p /usr/local/share/keyrings/ && \
  12 | >>>     wget -q -O - "https://repos.ripple.com/repos/api/gpg/key/public" | gpg --dearmor > ripple-key.gpg && \
  13 | >>>     mv ripple-key.gpg /usr/local/share/keyrings && \
  14 | >>>     echo "deb [signed-by=/usr/local/share/keyrings/ripple-key.gpg] https://repos.ripple.com/repos/rippled-deb focal stable" | tee -a /etc/apt/sources.list.d/ripple.list && \
  15 | >>>     apt-get update -y && \
  16 | >>>     apt-get install rippled -y && \
  17 | >>>     rm -rf /var/lib/apt/lists/* && \
  18 | >>>     export PATH=$PATH:/opt/ripple/bin/ && \
  19 | >>>     chmod +x /entrypoint.sh && \
  20 | >>>     echo '#!/bin/bash' > /usr/bin/server_info && echo '/entrypoint.sh server_info' >> /usr/bin/server_info && \
  21 | >>>     chmod +x /usr/bin/server_info
  22 |
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get update -y &&     apt-get install apt-transport-https ca-certificates wget gnupg -y &&     mkdir -p /usr/local/share/keyrings/ &&     wget -q -O - \"https://repos.ripple.com/repos/api/gpg/key/public\" | gpg --dearmor > ripple-key.gpg &&     mv ripple-key.gpg /usr/local/share/keyrings &&     echo \"deb [signed-by=/usr/local/share/keyrings/ripple-key.gpg] https://repos.ripple.com/repos/rippled-deb focal stable\" | tee -a /etc/apt/sources.list.d/ripple.list &&     apt-get update -y &&     apt-get install rippled -y &&     rm -rf /var/lib/apt/lists/* &&     export PATH=$PATH:/opt/ripple/bin/ &&     chmod +x /entrypoint.sh &&     echo '#!/bin/bash' > /usr/bin/server_info && echo '/entrypoint.sh server_info' >> /usr/bin/server_info &&     chmod +x /usr/bin/server_info" did not complete successfully: exit code: 100
Done, you can now run /Users/mbergen/Documents/Github/docker-rippled/go/up

The changes to `entrypoint.sh` are not reflected in the 1.11.0 image

This commit is not reflected in the latest image. 8315fc1

This is the contents of entrypoint.sh in latest and 1.11.0 images

#!/bin/bash

rippledconfig=`/bin/cat /config/rippled.cfg 2>/dev/null | wc -l`
validatorstxt=`/bin/cat /config/validators.txt 2>/dev/null | wc -l`

mkdir -p /config

if [[ "$rippledconfig" -gt "0" && "$validatorstxt" -gt "0" ]]; then

    echo "Existing rippled config at host /config/, using them."

    /bin/cat /config/rippled.cfg > /etc/opt/ripple/rippled.cfg
    /bin/cat /config/validators.txt > /etc/opt/ripple/validators.txt

fi

# Start rippled, Passthrough other arguments
exec /opt/ripple/bin/rippled --conf /etc/opt/ripple/rippled.cfg "$@"

It should be:

#!/bin/bash

echo "Args:"
echo "    >> [$@]"
echo ""
echo "Env Args:"
echo "    >> [$ENV_ARGS]"
echo ""
echo "Env:"
printenv
echo ""

rippledconfig=`/bin/cat /config/rippled.cfg 2>/dev/null | wc -l`
validatorstxt=`/bin/cat /config/validators.txt 2>/dev/null | wc -l`

mkdir -p /config

if [[ "$rippledconfig" -gt "0" ]]; then
    echo "Existing rippled config at host /config/, using."
    /bin/cat /config/rippled.cfg > /etc/opt/ripple/rippled.cfg
fi

if [[ "$validatorstxt" -gt "0" ]]; then
    echo "Existing validator config at host /config/, using."
    /bin/cat /config/validators.txt > /etc/opt/ripple/validators.txt
fi

# Start rippled, Passthrough other arguments
exec /opt/ripple/bin/rippled --conf /etc/opt/ripple/rippled.cfg $@$ENV_ARGS

I want to make an RPC call with Postman. please help me~!

I want to make an RPC call with Postman.
However, the RPC call does not work.
I'm using a docker image called (xrpllabsofficial/xrpld:latest).
I'll explain a scenario I've been working on.

Create a container
docker run -itd --name xrp_testvalidator -e TESTVAR=123123 --network medalla -p 40048:80 -p 40049:51235 -p 40050:5005 -p 40051:51234 -p 40052:6006 -p 40053:50051 -p 40054 :443 -v D:\docker\container\testnet\xrp_validator\config/:/config/ -v D:\docker\container\testnet\xrp_validator\db/:/var/lib/rippled/db/ xrpllabsofficial/xrpld: latest
Rippled.cfg and validators.txt used previously provided files, and are located in "D:\docker\container\testnet\xrp_validator\config".
RPC call
url : https://localhost:40048~40054 (post)
content:
{
"method": "ledger",
"params": [
{
"ledger_index": "validated",
"accounts": false,
"full": false,
"transactions": false,
"expand": false,
"owner_funds": false
}
]
}
Error content:
Error: Client network socket disconnected before secure TLS connection was established

please.
I want to run a Ripple node.
But it doesn't work as well as intended.
Please help me make RPC calls possible.

Loading: "/etc/opt/ripple/rippled.cfg"
2019-Jan-11 16:34:58.173321800 HTTPClient:NFO Connecting to 127.0.0.1:5005

         "server_state" : "full",

but when i connect ripple-lib to the server using the default config by port 80

im getting

UnhandledPromiseRejectionWarning: RippledNotInitializedError: Rippled not initialized
    at _disconnect.then (/Users/asiel.gil/Workspace/xrp-project/xrp-project-server/parse-server/node_modules/ripple-lib/dist/npm/common/connection.js:162:27)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:7566) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7566) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

No ledger found

Thanks for the docker image, I managed to pull and build a container successfully. However, I noticed that it connected to 10 peers but my ripple node got no ledger.

I got the following from server_info:
"published_ledger": "none",

May I know how do I got the distributed ledger?

Thanks