fides Quick Start Troubleshooting
See original GitHub issueBug Description
Hi fides team,
I’m trying to get fides up and running locally for the very first time but am having some problems. I hope you can help. Basically:
- I get WARN messages about variables not being set during quick start. Can I ignore these safely?
- Why does the first quick start build take ~ 10 minutes (592 seconds in installation log attached below)? This is not quick. Is there some way of speeding this up?
- The quick start guide says to wait until the
fides#
prompt appears. It never appears. - After
nox -s dev
is finished, how do I exit?
Steps to Reproduce
- Clean your Docker env to simulate a first time user’s experience
- Stop all running containers
docker stop $(docker ps -a -q)
- Remove all containers
docker rm $(docker ps -a -q)
- Prune all images
docker image prune -a
- Prune all volumes
docker volume prune
- Prune build cache
docker builder prune -a
.
- Stop all running containers
- Folllow fides quick start instructions here
- Try to reach the
fides init
part of Step 2 (I didn’t get pastnox -s dev
).
Expected behavior
- No WARN messages
- First-time quick start of ~ 3 minutes (this is the expected time stated in the docs)
- A
fides#
prompt (maybe I’m supposed todocker exec
into a running container or something?) - Guidance on how to exit / tear down quick start env.
Screenshots
I’m attaching the entire installation log here:
2022-10-12 daveqnet-alt fides quick start installation.log
The WARN messages were…
WARN[0000] The "VAULT_ADDR" variable is not set. Defaulting to a blank string.
WARN[0000] The "VAULT_TOKEN" variable is not set. Defaulting to a blank string.
WARN[0000] The "FIDES__CLI__ANALYTICS_ID" variable is not set. Defaulting to a blank string.
WARN[0000] The "VAULT_NAMESPACE" variable is not set. Defaulting to a blank string.
WARN[0000] The "FIDES__CLI__ANALYTICS_ID" variable is not set. Defaulting to a blank string.
Environment
- Version: v1.9.2, I think? Not sure given recent repo unification efforts. See below for exact commit to main
- OS: See below
- Python Version: See below
- Docker Version: See below
~/projects/github/ethyca/fides main ❯ git log -1 | head -n 3
commit eb958dad3e313b6787199c4454c9493ac3595406
Author: Adam Sachs <adam@ethyca.com>
Date: Tue Oct 11 17:02:09 2022 -0400
~/projects/github/ethyca/fides main ❯ system_profiler SPSoftwareDataType SPHardwareDataType
Software:
System Software Overview:
System Version: macOS 12.6 (21G115)
Kernel Version: Darwin 21.6.0
<redacted>
Hardware:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro17,1
Chip: Apple M1
Total Number of Cores: 8 (4 performance and 4 efficiency)
Memory: 16 GB
System Firmware Version: 7459.141.1
OS Loader Version: 7459.141.1
<redacted>
~/projects/github/ethyca/fides main ❯ python --version
Python 3.10.7
~/projects/github/ethyca/fides main ❯ nox --version
2022.8.7
~/projects/github/ethyca/fides main ❯ pipx --version
1.1.0
~/projects/github/ethyca/fides main ❯ docker --version
Docker version 20.10.17, build 100c701
~/projects/github/ethyca/fides main ❯ docker-compose --version
Docker Compose version v2.10.2
Additional context
This is obviously an issue raised by an alt of @daveqnet, but please treat it exactly the same as you would an issue raised by any non-Ethyca GitHub member
Issue Analytics
- State:
- Created a year ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Trouble shooting guide - FIDES DV-Partner
We always try to get the best out of every bug report. We will fix software developing related problems as soon as possible...
Read more >CAD Program "FiDES" Won't Launch on Laptop, 0xc000007b ...
I'm trying to load a CAD program called FiDES on a workstation of mine running Win10 and the program won't launch.
Read more >How to Fix iPhone Quick Start not Working Issue - iMobie
iPhone Quick Start is not working while you are setting up a new device? Solutions offered in our article might help you fix...
Read more >Avance - User's Reference Manual - Frank's Hospital Workshop
The user of this Product shall have the sole responsibility for any malfunction which results from improper use, faulty maintenance, improper repair, damage,...
Read more >Operator's Manual - Technical Documents
Intuitive, touchscreen navigation for easy and adaptable use in any hospital ... WARNING: Do not start or operate the Root unless the setup...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for your help on this, @sanders41!
After a
git pull
the build time in a cleaned Docker env (no cache) shrank to 158 seconds, which is a HUGE improvement. 🎉Using
nox -s dev -- shell
as you suggested also takes me to afides#
prompt. 🥳Just on the env teardown,
ctrl+c
in the container itself doesn’t work…but if I exit the container and then use
ctrl+c
it seems to work.Should I be concerned about the
nox > * dev: failed
message?Also, the volumes created during the quick start persist - is this intended?
Yes, you can safely ignore these. They are more info than warning, we might should change it to info.
This is an issue with M1/M2 macs that was just fixed. If you pull the latest
main
you will get this update.The quick start command is missing an argument. It should be
nox -s dev -- shell
. I have opened an issue for this here. This is the biggest part of your issue with completing the quick start. If you have any more issues afternox -s dev -- shell
feel free to follow-up with more questions.Control + c
will stop the container.