Hi there, I have problem running my application after switching confinement to classic. Is there any extra config that I should be aware of ?
Source code for snapcraft yml https://github.com/flow-lab/flow/blob/master/snap/snapcraft.yaml
I created a pull request to attempt to fix it. I built, installed and ran it locally and it works. However you may want to check the sanity of my fixes with @sergiusens when he’s back from vacation tomorrow. As I know there are some caveats around using the no-patchelf line. Without it, the binary segfaults.
Pulling flow
Cloning into '/root/build_flow/parts/flow/src'...
remote: Counting objects: 296, done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 296 (delta 7), reused 14 (delta 5), pack-reused 278
Receiving objects: 100% (296/296), 50.81 KiB | 0 bytes/s, done.
Resolving deltas: 100% (167/167), done.
Checking connectivity... done.
go get -t -d ./github.com/flow-lab/flow/...
Building flow
go build -o /root/build_flow/parts/flow/go/bin/flow github.com/flow-lab/flow
Staging flow
Priming flow
The primed files for part 'flow' will not be verified for correctness or patched: build-attributes: [no-patchelf] is set.
Stopping local:snapcraft-flow
Snapping 'flow' -
Snapped flow_master_amd64.snap
$ snap run flow --help
NAME:
development tooling for AWS - A new cli application
USAGE:
flow [global options] command [command options] [arguments...]
VERSION:
0.1.24
COMMANDS:
dynamodb
sqs
sns
cloudwatch
cloudwatchlogs
ssm
secretsmanager
help, h Shows a list of commands or help for one command
GLOBAL OPTIONS:
--help, -h show help
--version, -v print the version
1 Like
It works. Thank you a lot for helping me out with this issue.
1 Like