# Wave CLI authentication issues?

**URL:** <https://community.seqera.io/t/wave-cli-authentication-issues/2467>\
**Category:** Ask for help\
**Created:** [November 23, 2025, 6:49am UTC](https://community.seqera.io/t/wave-cli-authentication-issues/2467 "2025-11-23T06:49:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mpampuch](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mpampuch/32/729_2.png) [@mpampuch](https://community.seqera.io/u/mpampuch)\
**Post date:** [November 23, 2025, 6:49am UTC](https://community.seqera.io/t/wave-cli-authentication-issues/2467/1 "2025-11-23T06:49:34Z")

</div>

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](https://docs.seqera.io/wave/tutorials/wave-cli)

I’m running the following

```auto
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:

```auto
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:

```auto
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](https://wave.seqera.io/view/builds/bd-e45d4027cd9c03c5_1)

Singularity: [Container build report](https://wave.seqera.io/view/builds/bd-33295c4fbbde7ec4_2)

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`

```auto
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

```

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [November 24, 2025, 7:19pm UTC](https://community.seqera.io/t/wave-cli-authentication-issues/2467/2 "2025-11-24T19:19:31Z")

</div>

Answered in Slack: [Slack](https://nextflow.slack.com/archives/C0477AS31T5/p1764000760221319?thread_ts=1763560906.659829&channel=C0477AS31T5&message_ts=1764000760.221319)