Wave CLI authentication issues?

Ask for help
1

I’m having an issue with the wave cli (this is my first time using it). I seem to be getting authentication problems despite following all the instructions here: Wave CLI | Seqera Docs

I’m running the following

wave \
  -f Dockerfile \
  --context . \
  --platform linux/amd64 \
  --freeze \
  --build-repo docker.io/mpampuch/smudgeplot \
  --tower-token $TOWER_ACCESS_TOKEN \
  --tower-workspace-id 40230138858677 \
  --await \
  --log-level "INFO"
wave \
  -f Dockerfile \
  --context . \
  --singularity \
  --freeze \
  --build-repo docker.io/mpampuch/smudgeplot-singularity \
  --tower-token $TOWER_ACCESS_TOKEN \
  --tower-workspace-id 40230138858677 \
  --await \
  --log-level "INFO"

And I get the following errors:

Docker build:

error: failed to solve: failed to push docker.io/mpampuch/smudgeplot:e45d4027cd9c03c5: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

Singularity build:

Unable to build from /efs/wave/build/bd-33295c4fbbde7ec4_2/Containerfile: while parsing definition: /efs/wave/build/bd-33295c4fbbde7ec4_2/Containerfile: failed to parse deffile header: invalid header keyword found: from mambaorg/micromamba

Full logs here:

Docker: Container build report

Singularity: Container build report

The docker one especially confuses me because I even tried creating a personal access token on my dockerhub with read and write permissions, but I still got the same permissions error.

But the singularity one I’m confused by because I thought wave only needed a Dockerfile and could provision singularity containers straight from it? Was I mistaken? Do singularity container builds need to have a singularity definition file written by the developer?

Edit: Additionally, I noticed that for some reason, the credentials I put inside my seqera platform are not being used for whatever reason. Their last activity is never

Checking my credentials, it says my dockerhub credentials are not being used for some reason?
tw credentials list

  Credentials at user workspace:

     ID                     | Provider      | Name               | Last activity                 
    ------------------------+---------------+--------------------+-------------------------------
     2********************r | container-reg | dockerhub-creds-rw | never                         
     3********************m | container-reg | dockerhub-creds    | never                         
     6********************d | tw-agent      | ibex_connection    | Sun, 23 Nov 2025
2

Answered in Slack: Slack