receiving the following error when trying to start Macbook version of the app.

LocalStack Cockpit version: v0.2.1
LocalStack version: 2.1.1.dev
LocalStack Docker container id: 2091a5172071
LocalStack build date: 2023-06-26
LocalStack build git hash: 7e1346e0
Docker Daemon: Docker version 24.0.2, build cb74dfc
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 37 (Thirty Seven)
Release: 37
Codename: ThirtySeven

When running from the console, I see the following error:

10:50:47.128 › stdout: ERROR: '['docker', 'inspect', '--format', '{{json .}}', 'myhostname']': exit code 1; output: b'\nError: No such object: myhostname\n'
{"runtime_version": "2.1.1.dev", "image_tag": "latest", "image_id": 
"a6b86a621a96", "image_created": "2023-06-26T07:01:34", "running": true, 
"container_name": "localstack_main", "container_ip": "172.17.0.2"}

10:50:47.129 › SyntaxError: Unexpected token E in JSON at position 0
    at JSON.parse (<anonymous>)
    at t.parseStatusStdout (/tmp/.mount_LocalSz9URxz/resources/app.asar/dist/main/main.js:14:892681)
    at t.default.getStatus (/tmp/.mount_LocalSz9URxz/resources/app.asar/dist/main/main.js:14:888969)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at t.default.getAndSendStatus (/tmp/.mount_LocalSz9URxz/resources/app.asar/dist/main/main.js:14:896957)
    at i.handle (/tmp/.mount_LocalSz9URxz/resources/app.asar/dist/main/main.js:14:887466)
    at /tmp/.mount_LocalSz9URxz/resources/app.asar/dist/main/main.js:14:896721
10:50:47.587 › stdout: ERROR: '['docker', 'inspect', '--format', '{{json .}}', 'myhostname']': exit code 1; output: b'\nError: No such object: myhostname\n'
{"runtime_version": "2.1.1.dev", "image_tag": "latest", "image_id": 
"a6b86a621a96", "image_created": "2023-06-26T07:01:34", "running": true, 
"container_name": "localstack_main", "container_ip": "172.17.0.2"}

This error reflects what I see if I query docker directly with docker inspect myhostname:

[]
Error: No such object: myhostname

However, if I use docker inspect localstack_main then I see what you're probably looking for.

note: "myhostname" is a substitution for the actual host name

Checking Docker
Docker version 24.0.2, build cb74dfc
Could not detect a running Docker daemon. Please make sure that Docker is running.

[2023-06-12 12:03:43.198] [warn] error: Command failed: docker version
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/version": dial unix /var/run/docker.sock: connect: permission denied

Linux v0.2.1 (beta)

Hi Localstack Team -

Mac Os - 12.6 Monterey Intel
Cockpit version - LocalStack Cockpit-0.1.1.dmg
I downloaded and without moving it to applications, have put app in my personal folder.
It can recognize the docker from outside but cannot from inside localstack binary. I do not have docker desktop but using docker with lima and it works perfectly fine for every other application.
Restart doesn't work and if I try to close the application by x, it doesn't close and have to close using activity monitor.
I can run localstack using docker/pip without issues and can play with demo - localstack-demo

It is just not this application :(.

Hi,

I am getting error with Checking LocalStack Runtime Status that Docker is not available although it is available according to the screenshot

After copying the arm64 cockpit app to my Applications folder and attempting to open the app, I get the error:

“LocalStack Cockpit” is damaged and can’t be opened. You should move it to the Trash.

macOS Monterey 12.3.1
MacBook Pro (14-inch, 2021)
Apple M1 Max

app installer: LocalStack Cockpit 0.1.1-arm64.dmg

I tried setting the configuration environment variable for SERVICES on windows. It doesn't start the services specified.

As the title says, I am getting errors if I endeavor to use Cockpit and docker compose.

1. Using Stop produces this error message in the UI:

spawn C:\Users\marce\AppData\Local\Temp\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\resources\vendor\win32\localstack-packaged-cli\localstack.exe ENOENT

1,5. Furthermore, if I close the Cockpit, it stays open in the background. It needs to be manually stopped from the Task Manager.

Starting the Cockpit again and attempting to Stop the docker gives me this error:

Command failed: C:\Users\marce\AppData\Local\Temp\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\resources\vendor\win32\localstack-packaged-cli\localstack.exe stop
Python path configuration:
  PYTHONHOME = 'C:\Users\marce\AppData\Local\Temp\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\resources\vendor\win32\localstack-packaged-cli'
  PYTHONPATH = (not set)
  program name = 'C:\Users\marce\AppData\Local\Temp\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\resources\vendor\win32\localstack-packaged-cli\localstack.exe'
  isolated = 0
  environment = 0
  user site = 0
  import site = 0
  sys._base_executable = 'C:\\Users\\marce\\AppData\\Local\\Temp\\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\\resources\\vendor\\win32\\localstack-packaged-cli\\localstack.exe'
  sys.base_prefix = ''
  sys.base_exec_prefix = ''
  sys.platlibdir = 'lib'
  sys.executable = 'C:\\Users\\marce\\AppData\\Local\\Temp\\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\\resources\\vendor\\win32\\localstack-packaged-cli\\localstack.exe'
  sys.prefix = ''
  sys.exec_prefix = ''
  sys.path = [
    'C:\\Users\\marce\\AppData\\Local\\Temp\\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\\resources\\vendor\\win32\\localstack-packaged-cli\\base_library.zip',
    'C:\\Users\\marce\\AppData\\Local\\Temp\\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\\resources\\vendor\\win32\\localstack-packaged-cli\\lib-dynload',
    'C:\\Users\\marce\\AppData\\Local\\Temp\\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\\resources\\vendor\\win32\\localstack-packaged-cli',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00000d88 (most recent call first):
<no Python frame>

2. In one of the iterrations of the testing, I was able to stop the docker image with Cockpit, but if I set out to start it again I received this error:

Command failed: C:\Users\marce\AppData\Local\Temp\26OcbI6X3kmPRwg2ZrAtdaq6HYJ\resources\vendor\win32\localstack-packaged-cli\localstack.exe start --detached --no-banner
2022-03-16T15:06:30.348:INFO:localstack.utils.threads: Thread run method <function Server.do_start_thread.<locals>._run at 0x0000028F54691700>(None) failed: ('Docker process returned with errorcode 125', None, b'docker: Error response from daemon: Conflict. The container name "/localstack_main" is already in use by container "820d8292bad7854bd8671e3c68b9bdbc0d698b53c17c19edf2cbdd78ed21408b". You have to remove (or rename) that container to be able to reuse that name.\nSee \'docker run --help\'.\n') Traceback (most recent call last):
  File "localstack\utils\container_utils\docker_cmd_client.py", line 512, in _run_async_cmd
subprocess.CalledProcessError: Command '['docker', 'run', '--rm', '--name', 'localstack_main', '-v', 'C:\\Users\\marce\\AppData\\Local\\Temp\\localstack\\var_libs:/var/lib/localstack/var_libs', '-v', 'C:\\Users\\marce\\AppData\\Local\\Temp\\localstack\\cache:/var/lib/localstack/cache', '-v', 'C:\\Users\\marce\\AppData\\Local\\Temp\\localstack:/tmp/localstack', '-v', '/var/run/docker.sock:/var/run/docker.sock', '-p', '127.0.0.1:4566:4566', '-p', '127.0.0.1:4571:4571', '-p', '127.0.0.1:4510-4559:4510-4559', '-e', 'TEST_AWS_ACCOUNT_ID=000000000000', '-e', 'DEFAULT_REGION=us-east-1', '-e', 'DOCKER_HOST=unix:///var/run/docker.sock', '-e', 'HOST_TMP_FOLDER=C:\\Users\\marce\\AppData\\Local\\Temp\\localstack', '-e', 'SET_TERM_HANDLER=1', '--privileged', 'localstack/localstack']' returned non-zero exit status 125.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "localstack\utils\threads.py", line 38, in run
  File "localstack\utils\serving.py", line 168, in _run
  File "localstack\utils\bootstrap.py", line 577, in do_run
  File "localstack\utils\bootstrap.py", line 518, in run
  File "localstack\utils\container_utils\docker_cmd_client.py", line 442, in run_container
  File "localstack\utils\container_utils\docker_cmd_client.py", line 526, in _run_async_cmd
localstack.utils.container_utils.container_client.ContainerException: ('Docker process returned with errorcode 125', None, b'docker: Error response from daemon: Conflict. The container name "/localstack_main" is already in use by container "820d8292bad7854bd8671e3c68b9bdbc0d698b53c17c19edf2cbdd78ed21408b". You have to remove (or rename) that container to be able to reuse that name.\nSee \'docker run --help\'.\n')

[15:06:29] preparing environment                               bootstrap.py:743
           configuring container                               bootstrap.py:751
           starting container                                  bootstrap.py:757

I am a vision impaired user and am really strugging with the Cockpit with its current "Light" Theme.
This is making it extremely difficult to navigate the app and find items on the screen or even to work out how to use those items.

Ideally the app should offer a "Dark" theme like many other apps do these days.
This would probably include

• Dark/Black background
• Lighter (white not pale blue) coloured text and buttons
• In MacOs observing the Users choice of theme (Light/dark) and adjusting as required
• These are just initial thoughts

This would be very helpful for many users who also struggling with this colour scheme

Thanks for your understanding

Hi,

Cockpit shows that localstack is not running although localstack is running.

os: Ubuntu 22.04
LocalStack Version: 2.0.2
Cockpit: LocalStack Cockpit-0.2.1.AppImage

❯ localstack status
┌─────────────────┬───────────────────────────────────────────────────────┐
│ Runtime version │ 2.0.3.dev │
│ Docker image │ tag: latest, id: 3efd9e874805, 📆 2023-05-04T17:27:52 │
│ Runtime status │ ✔ running (name: "localstack_main", IP: 172.17.0.2) │
└─────────────────┴───────────────────────────────────────────────────────┘

Repro:

1. Get Download link from 0.1.1 beta from https://localstack.cloud/products/cockpit/
2. Go to e-mail, download LocalStack Cockpit 0.1.1.exe.msi
3. Open windows explorer and double click LocalStack Cockpit 0.1.1.exe

Expected behavior:
Cockpit starts

Actual behavior:

Resolution:
Either

• Change file extension from msi to exe in windows explorer and double-click, or
• Open git bash and run ./LocalStack\ Cockpit\ 0.1.1.exe.msi

After installing cockpit and starting up the services. The health check endpoint returns available but not in running status

localstack-cockpit % curl http://localhost:4566/health
{"services": {"acm": "available", "apigateway": "available", "cloudformation": "available", "cloudwatch": "available", "config": "available", "dynamodb": "available", "dynamodbstreams": "available", "ec2": "available", "es": "available", "events": "available", "firehose": "available", "iam": "available", "kinesis": "available", "kms": "available", "lambda": "available", "logs": "available", "opensearch": "available", "redshift": "available", "resource-groups": "available", "resourcegroupstaggingapi": "available", "route53": "available", "route53resolver": "available", "s3": "available", "s3control": "available", "secretsmanager": "available", "ses": "available", "sns": "available", "sqs": "available", "ssm": "available", "stepfunctions": "available", "sts": "available", "support": "available", "swf": "available", "transcribe": "available"}, "version": "2.1.1.dev"}%   bviswanathan@MAC-FVFH266MQ6LR localstack-cockpit % 

No logs are shown in the UI.

AVG Antivirus says that Windows installer ("LocalStack Cockpit 0.2.1.exe") is an IDP malware

this isn't critical (more like a friendly suggestion): On my Windows machine LocalStack Cockpit 0.1.1.exe triggered mutliple security popups and asked for excemptions (Browser after download, Windows SmartShield/Defender, Anti Malware). I don't mind, but in managed environments this can be a hassle.

I believe this would much improve if the installer and the binaries that it exctracts were codesigned with a cert from a trusted CA.

Currently it doesn't detect localstack that are crested using image from other registry like AWS ECR

We use localstack extensively using TestContainers, it'd be great if Cockpit could detect the existing running container so we could use it to view logs/check service status etc while debugging.

Hey,

It would be nice to register and verify LocalStack Cockpit app within Apple. I use corporate Macbook Pro and I don't want to bypass security settings in order to install Cockpit.

Hi, thanks for making localstack. Quite cool project!

The Cockpit, which I had to give out my email for... It doesn't really do anything. It looks like an ElectronJS app, but for how low-level it is. I might as well use a docker-compose.yml file.

On first start it complained a ~/.localstack folder was not available.

So I did mkdir -p ~/.localstack, and asked it to restart... The app did not restart.

Then once it did start it pulled localstack ignoring the localstack-full I had pulled.

Once it had pulled an image, it did not start it, or create a default profile.

Once the container was running, services was a reporting view, that gave no clear indication that I could change anything from that view. This was probably the most surprising thing.

So I created a profile (as it still had not)

Looks like environment var config. No autocompletes, no predetermined options. No blank UI states. No UI at all really.

I was just exploring. but I feel like maybe just focus on the docker side if this is working as intended.

From a business standpoint I was surprised there was no upselling of pro.

Hi,

I'm trying to start LocalStack Cockpit version 0.1.1 with a Pro trail, but it's not starting.

I'm using Ubuntu 21.10

When I try to start a configuration without the key the services start properly.
This is the configuration
LOCALSTACK_API_KEY={key} DEBUG=1

This is the error log could not connect to LocalStack health endpoint at http://localhost:4566

I'm using the community version of localstack and when I open cockpit I see this:

I already have the community edition why do I need download the pro?

With message: Couldn't detect the LocalStack CLI. Make sure it is installed and on your path. See [documentation](https://docs.localstack.cloud/get-started/#localstack-cli) for more information.

However, the localstack-cli is findable/usable within the terminal

➜ which localstack
/home/XXXXX/.local/bin/localstack

Sorry for the brevity of this report, but I did not see any means of gathering verbose logging from the app. Below are my system details.

Arch Linux
Kernel: Linux 5.16.14-arch1-1 x86_64
Shell: zsh 5.8.1
Memory: 62.4 GiB
CPU: Intel® Core™ i9-10885H CPU @ 5.300GHz × 16
GPU: Intel CometLake-H GT2 [UHD Graphics]
GPU: NVIDIA GeForce GTX 1650 Ti Mobile
Disk Capacity: 2.0 TB
Desktop Environment: GNOME 41.3
Windowing System: Wayland

Hi,

Option under File > Restart does not work. It just kills the LocalStack-Cockpit and does not start it again.
I am expecting that it should restart the program (stop the service and start anew).

I had used the emailed link to download cockpit as $env:USERPROFILE\Downloads\LocalStack Cockpit 0.1.1.exe. Initially I went to the properties and checked the "Unblock" checkbox, clicked "OK" and then double-clicked the file to run it. The app would start but did not show LocalStack as running (I had previously started it from the CLI) and if I tried to "START" from the UI I would immediately get an error message about "spawn C:... ENOENT". I ended up creating a directory at $env:LOCALAPPDATA\Programs\LocalStack and moved the file there as Cockpit.exe and then it worked just fine. I recommend adding some documentation for "installing" on Windows.