You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, sorry if this is not the correct place or if I'm the problem, I feel like I'm going mad, and it might be because of an authorization issue.
We've been using dagster plus serverless for a while without issue, but for some reason I cannot seem to deploy anymore, and I'm the only one in my team affected by this issue.
I tried it all: regenerating the token, inputting it manually, logging in from the browser, deinstalling and reinstalling dagster cloud, deleting my env and rebuilding from scratch, I even logged in using the work google account of one of my colleagues (he can deploy no issues): I still get, right after the docker build is done: denied: Your authorization token has expired. Reauthenticate and try again.
Here is the shell script I use, it works just fine for my colleagues, and worked for me until a few days ago:
#!/bin/bash
# see https://github.com/dagster-io/dagster/discussions/12180
if [ -d ".venv" ]; then
echo ".venv already exists. Activating ..."
else
echo "Creating .venv"
python3 -m venv .venv
echo "Activating .venv..."
fi
source .venv/bin/activate
echo "Installing to .venv"
pip install -e .
# Dbt cleaning, deps install and parsing
cd dbt_audio
echo "Cleaning and rebuilding dbt project..."
dbt clean
dbt deps
dbt parse
cd ..
echo "Deploying to dagster+..."
dagster-cloud serverless deploy-docker \
--base-image python:3.11-slim \
--working-directory . \
--deployment prod \
--location-name audio_calls \
--package-name dagster_calls
And the relevant part of the output I always get:
Deploying to dagster+...
Docker version 27.2.0, build 3ab4256
[+] Building 22.8s (15/15) FINISHED docker:desktop-linux
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 1.56kB 0.0s
=> [internal] load metadata for docker.io/library/p 1.0s
=> [auth] library/python:pull token for registry-1. 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [1/9] FROM docker.io/library/python:3.11-slim@sh 0.0s
=> [internal] load build context 2.6s
=> => transferring context: 97.10MB 2.3s
=> CACHED [2/9] COPY *dagster_cloud_pre_install.sh 0.0s
=> CACHED [3/9] RUN if [ -f "dagster_cloud_pre_inst 0.0s
=> CACHED [4/9] RUN if [ -f "setup.py" ]; then 0.0s
=> CACHED [5/9] WORKDIR /opt/dagster/app 0.0s
=> [6/9] COPY . /opt/dagster/app 8.3s
=> [7/9] RUN if [ -f "requirements.txt" ]; then 0.1s
=> [8/9] RUN if [ -f "dagster_cloud_post_install.sh 3.1s
=> [9/9] RUN if ! dagster-cloud --version; then 1.7s
=> exporting to image 5.7s
=> => exporting layers 5.7s
=> => writing image sha256:7d7b1bdae5303c4b799fa9b2 0.0s
=> => naming to 657821118200.dkr.ecr.us-west-2.amaz 0.0s
View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/sojdy5pgncjuwk01f5z2uoe8b
What's next:
View a summary of image vulnerabilities and recommendations → docker scout quickview
The push refers to repository [657821118200.dkr.ecr.us-west-2.amazonaws.com/serverless-agent-db9cf710-cebb-356d-a87e-03ab94d8378a]
b5d85b507f07: Preparing
c93cd88f203d: Preparing
0a6625922b2a: Preparing
0c9b3938c77d: Preparing
473b2fc0da34: Preparing
e938cf83023d: Waiting
aa9081009d69: Waiting
0220c9084b1f: Waiting
b37145d52b36: Waiting
5b2bbb7d3a14: Waiting
1eae3090c894: Waiting
8d853c8add5d: Waiting
denied: Your authorization token has expired. Reauthenticate and try again.
The text was updated successfully, but these errors were encountered:
Hi, sorry if this is not the correct place or if I'm the problem, I feel like I'm going mad, and it might be because of an authorization issue.
We've been using dagster plus serverless for a while without issue, but for some reason I cannot seem to deploy anymore, and I'm the only one in my team affected by this issue.
I tried it all: regenerating the token, inputting it manually, logging in from the browser, deinstalling and reinstalling dagster cloud, deleting my env and rebuilding from scratch, I even logged in using the work google account of one of my colleagues (he can deploy no issues): I still get, right after the docker build is done:
denied: Your authorization token has expired. Reauthenticate and try again.
Here is the shell script I use, it works just fine for my colleagues, and worked for me until a few days ago:
And the relevant part of the output I always get:
The text was updated successfully, but these errors were encountered: