how to build a mainnet docker image

[appop]

I want to build a docker image for the mainnet, how to add PROFILE to env,

After I use the default command, I found it's only a dev net.

[madninja]

what is a dev net? the docker image is for main net ?

[appop]

@madninja I want to build a docker image for mainnet But I got error below.

etl_data/log/crash.log

`2021-11-22 02:34:30 =SUPERVISOR REPORT==== Supervisor: {<0.7603.11>,libp2p_simple_sup} Context: shutdown_error Reason: noproc Offender: [{pid,<0.7761.11>},{id,5},{mfargs,{libp2p_yamux_stream,open_stream,undefined}},{restart_type,temporary},{shutdown,1000},{child_type,worker}]

2021-11-22 02:47:34 =SUPERVISOR REPORT==== Supervisor: {<0.8941.11>,libp2p_simple_sup} Context: shutdown_error Reason: noproc Offender: [{pid,<0.8827.11>},{id,1},{mfargs,{libp2p_yamux_stream,open_stream,undefined}},{restart_type,temporary},{shutdown,1000},{child_type,worker}]

2021-11-22 03:00:39 =SUPERVISOR REPORT==== Supervisor: {<0.10377.11>,libp2p_simple_sup} Context: shutdown_error Reason: noproc Offender: [{pid,<0.10395.11>},{id,5},{mfargs,{libp2p_yamux_stream,open_stream,undefined}},{restart_type,temporary},{shutdown,1000},{child_type,worker}]

2021-11-22 03:08:42 =SUPERVISOR REPORT==== Supervisor: {<0.9626.11>,libp2p_simple_sup} Context: shutdown_error Reason: noproc Offender: [{pid,<0.11039.11>},{id,19},{mfargs,{libp2p_yamux_stream,open_stream,undefined}},{restart_type,temporary},{shutdown,1000},{child_type,worker}]`

etl_data/log/error.log

2021-11-22 02:23:26.640 [error] <0.5343.11> Supervisor {<0.5343.11>,libp2p_simple_sup} had child 1 started with {libp2p_yamux_stream,receive_stream,undefined} at <0.6515.11> exit with reason noproc in context shutdown_error 2021-11-22 02:27:42.040 [error] <0.7043.11> Supervisor {<0.7043.11>,libp2p_simple_sup} had child 1 started with {libp2p_yamux_stream,receive_stream,undefined} at <0.7035.11> exit with reason noproc in context shutdown_error 2021-11-22 02:34:23.513 [error] <0.6616.11> Supervisor {<0.6616.11>,libp2p_simple_sup} had child 17 started with {libp2p_yamux_stream,open_stream,undefined} at <0.7788.11> exit with reason noproc in context shutdown_error 2021-11-22 02:34:30.390 [error] <0.7603.11> Supervisor {<0.7603.11>,libp2p_simple_sup} had child 5 started with {libp2p_yamux_stream,open_stream,undefined} at <0.7761.11> exit with reason noproc in context shutdown_error 2021-11-22 02:34:43.525 [error] <0.7828.11>@libp2p_transport_proxy:connect_to:69 failed to dial proxy server "/p2p/112uf8sh88EjwFAzt2Y1Cy5cxG5rcTLZSK11y3hHVMqn2UxS2BKk" not_found 2021-11-22 02:47:34.981 [error] <0.8941.11> Supervisor {<0.8941.11>,libp2p_simple_sup} had child 1 started with {libp2p_yamux_stream,open_stream,undefined} at <0.8827.11> exit with reason noproc in context shutdown_error 2021-11-22 03:00:39.499 [error] <0.10377.11> Supervisor {<0.10377.11>,libp2p_simple_sup} had child 5 started with {libp2p_yamux_stream,open_stream,undefined} at <0.10395.11> exit with reason noproc in context shutdown_error 2021-11-22 03:08:42.843 [error] <0.9626.11> Supervisor {<0.9626.11>,libp2p_simple_sup} had child 19 started with {libp2p_yamux_stream,open_stream,undefined} at <0.11039.11> exit with reason noproc in context shutdown_error

[madninja]

None of those errors are useful, they just represent normal networking output. You'll have to look in console.log to see if you are actually syncing. I would suggest you use a DeWi Postgres/blockchain.db dump combo to bootstrap your data since otherwise it will take very very long to sync from scratch.

Please join us on Discord in the blockchain-development channel. This is not the best mechanism to get support and is reserved for actual bug reports