Skip to content

docker image getting closed automatically... #2

@nantu002

Description

@nantu002

---- CHECKING PORT AVAILABILITY ----

Port 8080 is already free and available.

---- STARTING AZTEC NODE ----

Aztec node started successfully in a screen session.

diplapy@diplapy:$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
63d158fded65 aztecprotocol/aztec:latest "node --no-warnings …" 9 seconds ago Up 9 seconds 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 0.0.0.0:40400->40400/tcp, [::]:40400->40400/tcp, 0.0.0.0:40400->40400/udp, [::]:40400->40400/udp aztec-start-07c61259
diplapy@diplapy:
$ screen -ls
There are screens on:
1250224.aztec (05/03/25 04:10:40) (Detached)
1239129.aztec (05/02/25 20:48:43) (Detached)
2 Sockets in /run/screen/S-diplapy.
diplapy@diplapy:$ docker logs 63d158fded65
Error response from daemon: No such container: 63d158fded65
diplapy@diplapy:
$ sudo docker logs -f --tail 100 $(docker ps -q --filter ancestor=aztecprotocol/aztec:latest | head -n 1)
docker: 'docker logs' requires 1 argument

Usage: docker logs [OPTIONS] CONTAINER

Run 'docker logs --help' for more information
diplapy@diplapy:~$

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions