@Basilisvirus I’ve taken a look, and it appears you have two separate Resin accounts. You have an account registered with your email, which you’re using with the CLI, and a separate account registered to your github which you’ve been using in the UI.
You can see the username you’re using on the command line with
resin whoami and in the dashboard in the dropdown in the top right. If your username is prefixed with
gh_, that means it’s a github accont.
If you run
resin login in the CLI, and choose web authentication instead of manually entering your details, then it’ll authenticate immediately via your browser, and you’re guaranteed to end up using the same account you’re logged into in the dashboard.
On the CLI commands: yes,
resin build isn’t what you want - that lets you do a Docker build directly locally, and push the resulting container to Resin.io.
The problem with the first
local deploy commands there is the missing
. at the end. If should be:
resin local push -fs .
s . is a shortened version of
--source ., which is what you’re actually doing in the later command.
The 2nd problem is that right now the CLI only supports simple Dockerfiles, and the simple-server-node project uses a Dockerfile.template file. That will be added soon, but right now you’ll have to untemplate it by hand. To do that:
%%RESIN_MACHINE_NAME%% in the template file with
raspberrypi3 (assuming that’s the type of device you’re using)
- Rename the file to simply
Dockerfile (i.e. remove the
I am planning to look at tweaking & improving the UX of some of these commands in future, I’ll definitely be taking this into account in the design there!